Techniques for intra-user equipment and inter-user equipment cancelation of overlapping communications

ABSTRACT

Methods, systems, and devices for wireless communications are described. Wireless communications systems may employ one or more scheduling constraints to support efficient utilization of techniques for intra-device handling of overlapping scheduled uplink transmissions (e.g., intra-device dynamic resource cancelation and multiplexing) as well as inter-device handling of overlapping scheduled uplink transmissions (e.g., inter-device dynamic resource cancelation and multiplexing). Scheduling constraints may define how a device may apply intra-device and inter-device multiplexing and cancelation rules for various scenarios. For example, a device may apply intra-UE cancelation rules before inter-device cancelation rules. In some examples, later-received grants or uplink preemption indications (ULPIs) may not change a device&#39;s previously established decision to drop an uplink transmission. As another example, a device may not expect to receive a grant for an uplink transmission that would arise in subsequent cancelation of that uplink transmission due to a previously-received grant or previously-received ULPI.

CROSS REFERENCE

The present Application for Patent is a Continuation of U.S. patentapplication Ser. No. 17/174,272 by YANG et al., now issued as U.S. Pat.No. 11,490,414, entitled “TECHNIQUES FOR INTRAUSER EQUIPMENT ANDINTER-USER EQUIPMENT CANCELATION OF OVERLAPPING COMMUNICATIONS” filedFeb. 11, 2021, which claims the benefit of U.S. Provisional PatentApplication No. 62/977,080 by YANG et al., entitled “TECHNIQUES FORINTRA-USER EQUIPMENT AND INTER-USER EQUIPMENT CANCELLATION OFOVERLAPPING COMMUNICATIONS,” filed Feb. 14, 2020, each of which areassigned to the assignee hereof, and each of which are expresslyincorporated by reference herein.

FIELD OF TECHNOLOGY

The following relates generally to wireless communications and morespecifically to techniques for intra-user equipment (UE) and inter-UEcancelation of overlapping communications.

BACKGROUND

Wireless communications systems are widely deployed to provide varioustypes of communication content such as voice, video, packet data,messaging, broadcast, and so on. These systems may be capable ofsupporting communication with multiple users by sharing the availablesystem resources (e.g., time, frequency, and power). Examples of suchmultiple-access systems include fourth generation (4G) systems such asLong-Term Evolution (LTE) systems, LTE-Advanced (LTE-A) systems, orLTE-A Pro systems, and fifth generation (5G) systems which may bereferred to as New Radio (NR) systems. These systems may employtechnologies such as code division multiple access (CDMA), time divisionmultiple access (TDMA), frequency division multiple access (FDMA),orthogonal frequency division multiple access (OFDMA), or discreteFourier transform spread orthogonal frequency division multiplexing(DFT-S-OFDM). A wireless multiple-access communications system mayinclude one or more base stations or one or more network access nodes,each simultaneously supporting communication for multiple communicationdevices, which may be otherwise known as user equipment (UE).

Some wireless communications systems, such as NR systems, may supportheterogeneous conditions for one or more service deployments. Forexample, communication devices, such as a base station or a UE, maysupport flexibility in allocating multiple supported services or traffictypes over resources of a channel. As part of the allocation of channelresources, a base station and a UE may support the prioritization ofsome communications over others, which may include prioritization oftraffic or services having different reliability thresholds, differentlatency thresholds, or both. In some cases, efficient system utilizationmay be based on how resources are shared or allocated between differenttraffic types, or how UEs are configured according to different traffictypes.

SUMMARY

The described techniques relate to improved methods, systems, devices,and apparatuses that support techniques for intra-user equipment (UE)and inter-UE cancelation of overlapping communications. Generally, thedescribed techniques provide for one or more scheduling constraints thatmay be defined regarding uplink transmissions (e.g., such as overlappingphysical uplink shared channel (PUSCH) and physical uplink controlchannel (PUCCH) transmissions). For example, some wirelesscommunications systems may support techniques for intra-UE handling ofoverlapping scheduled uplink transmissions (e.g., intra-UE multiplexing)as well as inter-UE handling of overlapping scheduled uplinktransmissions (e.g., inter-UE multiplexing). Further, as describedherein, wireless communications systems may employ one or morescheduling constraints to support efficient utilization of suchtechniques for intra-UE and inter-UE handling of overlapping scheduledtransmissions.

For instance, the described techniques may provide for schedulingconstraints that may define how a UE may apply intra-UE and inter-UEmultiplexing and cancelation rules in various scenarios. For example, aUE may apply intra-UE cancelation rules (e.g., potentially resulting ina dropped uplink transmission) before inter-UE cancelation rules. Insome examples, later-received grants or later-received uplink preemptionindications (ULPIs) may not change the UE's decision to drop the uplinktransmission. As another example of a scheduling constraint, a UE maynot expect to receive a grant for an uplink transmission that wouldarise in subsequent cancelation of that uplink transmission due to apreviously-received grant or previously-received uplink preemptionindication (ULPI).

A method of wireless communication at a UE is described. The method mayinclude receiving a first grant for a first uplink transmissionscheduled for transmission by the UE, identifying that the first uplinktransmission at least partially overlaps with a second uplinktransmission also scheduled for transmission by the UE, and determiningto drop the second uplink transmission based on a first schedulingconstraint to resolve overlapping between the first uplink transmissionand the second uplink transmission, where the first schedulingconstraint is based at least in part on a first priority of the firstuplink transmission being greater than a second priority of the seconduplink transmission. The method may further include transmitting uplinkdata transmissions in accordance with a second scheduling constraint,where the second scheduling constraint relates to an additional uplinktransmission scheduled by an additional grant received after the firstgrant and scheduled to at least partially overlap with the first uplinktransmission, and where the second scheduling constraint is evaluatedafter satisfaction of the first scheduling constraint to resolveoverlapping between the additional uplink transmission and the firstuplink transmission after resolving overlapping between the first uplinktransmission and the second uplink transmission.

An apparatus for wireless communication at a UE is described. Theapparatus may include a processor, memory coupled with the processor,and instructions stored in the memory. The instructions may beexecutable by the processor to cause the apparatus to receive a firstgrant for a first uplink transmission scheduled for transmission by theUE, identify that the first uplink transmission at least partiallyoverlaps with a second uplink transmission also scheduled fortransmission by the UE, determine to drop the second uplink transmissionbased on a first scheduling constraint to resolve overlapping betweenthe first uplink transmission and the second uplink transmission, wherethe first scheduling constraint is based at least in part a firstpriority of the first uplink transmission being greater than a secondpriority of the second uplink transmission, and transmit uplink datatransmissions in accordance with a second scheduling constraint, wherethe second scheduling constraint relates to an additional uplinktransmission scheduled by an additional grant received after the firstgrant and scheduled to at least partially overlap with the first uplinktransmission, and where the second scheduling constraint is evaluatedafter satisfaction of the first scheduling constraint to resolveoverlapping between the additional uplink transmission and the firstuplink transmission after resolving overlapping between the first uplinktransmission and the second uplink transmission.

Another apparatus for wireless communication at a UE is described. Theapparatus may include means for receiving a first grant for a firstuplink transmission scheduled for transmission by the UE, identifyingthat the first uplink transmission at least partially overlaps with asecond uplink transmission also scheduled for transmission by the UE,determining to drop the second uplink transmission based on a firstscheduling constraint to resolve overlapping between the first uplinktransmission and the second uplink transmission, where the firstscheduling constraint is based at least in part a first priority of thefirst uplink transmission being greater than a second priority of thesecond uplink transmission, and transmitting uplink data transmissionsin accordance with a second scheduling constraint, where the secondscheduling constraint relates to an additional uplink transmissionscheduled by an additional grant received after the first grant andscheduled to at least partially overlap with the first uplinktransmission, and where the second scheduling constraint is evaluatedafter satisfaction of the first scheduling constraint to resolveoverlapping between the additional uplink transmission and the firstuplink transmission after resolving overlapping between the first uplinktransmission and the second uplink transmission.

A non-transitory computer-readable medium storing code for wirelesscommunication at a UE is described. The code may include instructionsexecutable by a processor to receive a first grant for a first uplinktransmission scheduled for transmission by the UE, identify that thefirst uplink transmission at least partially overlaps with a seconduplink transmission also scheduled for transmission by the UE, determineto drop the second uplink transmission based on a first schedulingconstraint to resolve overlapping between the first uplink transmissionand the second uplink transmission, where the first schedulingconstraint is based at least in part a first priority of the firstuplink transmission being greater than a second priority of the seconduplink transmission, and transmit uplink data transmissions inaccordance with a second scheduling constraint, where the secondscheduling constraint relates to an additional uplink transmissionscheduled by an additional grant received after the first grant andscheduled to at least partially overlap with the first uplinktransmission, and where the second scheduling constraint is evaluatedafter satisfaction of the first scheduling constraint to resolveoverlapping between the additional uplink transmission and the firstuplink transmission after resolving overlapping between the first uplinktransmission and the second uplink transmission.

Some examples of the method, apparatuses, and non-transitorycomputer-readable medium described herein may further includeoperations, features, means, or instructions for receiving theadditional grant, and ignoring the received additional grant based onthe second scheduling constraint until overlapping between the firstuplink transmission and the second uplink transmission is resolved,where the second uplink transmission may be dropped based on theignoring.

Some examples of the method, apparatuses, and non-transitorycomputer-readable medium described herein may further includeoperations, features, means, or instructions for receiving theadditional grant for the additional uplink transmission scheduled fortransmission by the UE, and determining to drop the first uplinktransmission based on the additional uplink transmission at leastpartially overlapping with the first uplink transmission, where thesecond uplink transmission and the additional uplink transmission may benon-overlapping.

In some examples of the method, apparatuses, and non-transitorycomputer-readable medium described herein, transmitting the uplink datatransmissions in accordance with the second scheduling constraint mayinclude operations, features, means, or instructions for piggybacking atleast a portion of the first uplink transmission on to the additionaluplink transmission based on the determination to drop the first uplinktransmission, and transmitting the additional uplink transmission andthe piggybacked portion of the first uplink transmission, where thedetermination to drop the second uplink transmission may be maintainedbased on the second scheduling constraint.

In some examples of the method, apparatuses, and non-transitorycomputer-readable medium described herein, the first uplink transmissionincludes a high priority uplink control channel transmission or a highpriority uplink shared channel transmission. In some examples of themethod, apparatuses, and non-transitory computer-readable mediumdescribed herein, the second uplink transmission includes a low priorityuplink control channel transmission, a low priority uplink sharedchannel transmission, or a sounding reference signal transmission. Insome examples of the method, apparatuses, and non-transitorycomputer-readable medium described herein, the additional uplinktransmission includes an additional high priority uplink transmission.In some examples of the method, apparatuses, and non-transitorycomputer-readable medium described herein, the additional grant includesa group-common grant, an uplink cancelation indication, or a slot formatindicator.

A method of wireless communication at a UE is described. The method mayinclude identifying that a first uplink transmission scheduled fortransmission by the UE at least partially overlaps with a second uplinktransmission also scheduled for transmission by the UE, receiving anuplink cancelation indication for a frequency-time resource that atleast partially overlaps with the first uplink transmission, determiningto drop the second uplink transmission based on a scheduling constraintto resolve overlapping between the first uplink transmission and thesecond uplink transmission, where the scheduling constraint is based atleast in part on a first priority of the first uplink transmission beinggreater than a second priority of the second uplink transmission, andapplying the uplink cancelation indication to the first uplinktransmission after determining that the scheduling constraint issatisfied.

An apparatus for wireless communication at a UE is described. Theapparatus may include a processor, memory coupled with the processor,and instructions stored in the memory. The instructions may beexecutable by the processor to cause the apparatus to identify that afirst uplink transmission scheduled for transmission by the UE at leastpartially overlaps with a second uplink transmission also scheduled fortransmission by the UE, receive an uplink cancelation indication for afrequency-time resource that at least partially overlaps with the firstuplink transmission, determine to drop the second uplink transmissionbased on a scheduling constraint to resolve overlapping between thefirst uplink transmission and the second uplink transmission, where thescheduling constraint is based at least in part on a first priority ofthe first uplink transmission being greater than a second priority ofthe second uplink transmission, and apply the uplink cancelationindication to the first uplink transmission after determining that thescheduling constraint is satisfied.

Another apparatus for wireless communication at a UE is described. Theapparatus may include means for identifying that a first uplinktransmission scheduled for transmission by the UE at least partiallyoverlaps with a second uplink transmission also scheduled fortransmission by the UE, receiving an uplink cancelation indication for afrequency-time resource that at least partially overlaps with the firstuplink transmission, determining to drop the second uplink transmissionbased on a scheduling constraint to resolve overlapping between thefirst uplink transmission and the second uplink transmission, where thescheduling constraint is based at least in part on a first priority ofthe first uplink transmission being greater than a second priority ofthe second uplink transmission, and applying the uplink cancelationindication to the first uplink transmission after determining that thescheduling constraint is satisfied.

A non-transitory computer-readable medium storing code for wirelesscommunication at a UE is described. The code may include instructionsexecutable by a processor to identify that a first uplink transmissionscheduled for transmission by the UE at least partially overlaps with asecond uplink transmission also scheduled for transmission by the UE,receive an uplink cancelation indication for a frequency-time resourcethat at least partially overlaps with the first uplink transmission,determine to drop the second uplink transmission based on a schedulingconstraint to resolve overlapping between the first uplink transmissionand the second uplink transmission, where the scheduling constraint isbased at least in part on a first priority of the first uplinktransmission being greater than a second priority of the second uplinktransmission, and apply the uplink cancelation indication to the firstuplink transmission after determining that the scheduling constraint issatisfied.

In some examples of the method, apparatuses, and non-transitorycomputer-readable medium described herein, applying the uplinkcancelation indication to the first uplink transmission may includeoperations, features, means, or instructions for determining to drop thefirst uplink transmission based on the frequency-time resource at leastpartially overlapping with the first uplink transmission. In someexamples of the method, apparatuses, and non-transitorycomputer-readable medium described herein, applying the uplinkcancelation indication to the first uplink transmission may includeoperations, features, means, or instructions for determining to transmitthe first uplink transmission even though the frequency-time resource atleast partially overlaps with the first uplink transmission.

In some examples of the method, apparatuses, and non-transitorycomputer-readable medium described herein, the first uplink transmissionincludes a high priority uplink control channel transmission or a highpriority uplink shared channel transmission. In some examples of themethod, apparatuses, and non-transitory computer-readable mediumdescribed herein, the second uplink transmission includes a low priorityuplink control channel transmission, a low priority uplink sharedchannel transmission, or a sounding reference signal transmission.

A method of wireless communication at a UE is described. The method mayinclude receiving a first grant for a first uplink transmissionscheduled for transmission by the UE, receiving, after receipt of thefirst grant, a second grant for a second uplink transmission scheduledfor transmission by the UE, determining that the first uplinktransmission and the second uplink transmission are scheduled so as tosatisfy a scheduling constraint that is based on a first priority of thefirst uplink transmission being greater than a second priority of thesecond uplink transmission, the scheduling constraint further based onwhether the first uplink transmission overlaps with the second uplinktransmission, and transmitting the first uplink transmission or thesecond uplink transmission based on satisfaction of the schedulingconstraint.

An apparatus for wireless communication at a UE is described. Theapparatus may include a processor, memory coupled with the processor,and instructions stored in the memory. The instructions may beexecutable by the processor to cause the apparatus to receive a firstgrant for a first uplink transmission scheduled for transmission by theUE, receive, after receipt of the first grant, a second grant for asecond uplink transmission scheduled for transmission by the UE,determine that the first uplink transmission and the second uplinktransmission are scheduled so as to satisfy a scheduling constraint thatis based on a first priority of the first uplink transmission beinggreater than a second priority of the second uplink transmission, thescheduling constraint further based on whether the first uplinktransmission overlaps with the second uplink transmission, and transmitthe first uplink transmission or the second uplink transmission based onsatisfaction of the scheduling constraint.

Another apparatus for wireless communication at a UE is described. Theapparatus may include means for receiving a first grant for a firstuplink transmission scheduled for transmission by the UE, receiving,after receipt of the first grant, a second grant for a second uplinktransmission scheduled for transmission by the UE, determining that thefirst uplink transmission and the second uplink transmission arescheduled so as to satisfy a scheduling constraint that is based on afirst priority of the first uplink transmission being greater than asecond priority of the second uplink transmission, the schedulingconstraint further based on whether the first uplink transmissionoverlaps with the second uplink transmission, and transmitting the firstuplink transmission or the second uplink transmission based onsatisfaction of the scheduling constraint.

A non-transitory computer-readable medium storing code for wirelesscommunication at a UE is described. The code may include instructionsexecutable by a processor to receive a first grant for a first uplinktransmission scheduled for transmission by the UE, receive, afterreceipt of the first grant, a second grant for a second uplinktransmission scheduled for transmission by the UE, determine that thefirst uplink transmission and the second uplink transmission arescheduled so as to satisfy a scheduling constraint that is based on afirst priority of the first uplink transmission being greater than asecond priority of the second uplink transmission, the schedulingconstraint further based on whether the first uplink transmissionoverlaps with the second uplink transmission, and transmit the firstuplink transmission or the second uplink transmission based onsatisfaction of the scheduling constraint.

In some examples of the method, apparatuses, and non-transitorycomputer-readable medium described herein, transmitting the first uplinktransmission or the second uplink transmission based on satisfaction ofthe scheduling constraint may include operations, features, means, orinstructions for transmitting the first uplink transmission. Someexamples of the method, apparatuses, and non-transitorycomputer-readable medium described herein may further includeoperations, features, means, or instructions for identifying that the UEmay have data to be included in the first uplink transmission, where thefirst uplink transmission may be transmitted based on the UE having datato be included in the first uplink transmission. Some examples of themethod, apparatuses, and non-transitory computer-readable mediumdescribed herein may further include operations, features, means, orinstructions for discarding the received second grant based on thescheduling constraint, where the first uplink transmission may betransmitted based on the discarding.

In some examples of the method, apparatuses, and non-transitorycomputer-readable medium described herein, the first grant includes adynamic high priority grant. In some examples of the method,apparatuses, and non-transitory computer-readable medium describedherein, transmitting the first uplink transmission or the second uplinktransmission based on satisfaction of the scheduling constraint mayinclude operations, features, means, or instructions for transmittingthe second uplink transmission. Some examples of the method,apparatuses, and non-transitory computer-readable medium describedherein may further include operations, features, means, or instructionsfor determining to skip the first uplink transmission based on a bufferstatus of the UE being below a threshold, where the second uplinktransmission may be transmitted based on the determination to skip thefirst uplink transmission.

In some examples of the method, apparatuses, and non-transitorycomputer-readable medium described herein, the first uplink transmissionincludes a high priority scheduling request or a high priority uplinkconfigured grant transmission. In some examples of the method,apparatuses, and non-transitory computer-readable medium describedherein, the scheduling constraint may be satisfied based on the firstuplink transmission and the second uplink transmission beingnon-overlapping.

In some examples of the method, apparatuses, and non-transitorycomputer-readable medium described herein, the first uplink transmissioncomprises a hybrid automatic repeat request acknowledgment transmissionor a channel state information transmission. In some examples of themethod, apparatuses, and non-transitory computer-readable mediumdescribed herein, the scheduling constraint provides that the UE doesnot expect to receive a grant scheduling a low priority uplinktransmission that overlaps with a previously scheduled high priorityuplink transmission.

A method of wireless communication at a UE is described. The method mayinclude receiving an uplink cancelation indication for a firstfrequency-time resource, receiving, after receipt of the uplinkcancelation indication, a grant for an uplink transmission scheduled fortransmission by the UE in a second frequency-time resource, determiningthat the uplink transmission is scheduled so as to satisfy a schedulingconstraint that is based on whether the first frequency-time resourceoverlaps with the second frequency-time resource, and determining topreempt the first frequency-time resource and transmit the uplinktransmission based on satisfaction of the scheduling constraint.

An apparatus for wireless communication at a UE is described. Theapparatus may include a processor, memory coupled with the processor,and instructions stored in the memory. The instructions may beexecutable by the processor to cause the apparatus to receive an uplinkcancelation indication for a first frequency-time resource, receive,after receipt of the uplink cancelation indication, a grant for anuplink transmission scheduled for transmission by the UE in a secondfrequency-time resource, determine that the uplink transmission isscheduled so as to satisfy a scheduling constraint that is based onwhether the first frequency-time resource overlaps with the secondfrequency-time resource, and determine to preempt the firstfrequency-time resource and transmit the uplink transmission based onsatisfaction of the scheduling constraint.

Another apparatus for wireless communication at a UE is described. Theapparatus may include means for receiving an uplink cancelationindication for a first frequency-time resource, receiving, after receiptof the uplink cancelation indication, a grant for an uplink transmissionscheduled for transmission by the UE in a second frequency-timeresource, determining that the uplink transmission is scheduled so as tosatisfy a scheduling constraint that is based on whether the firstfrequency-time resource overlaps with the second frequency-timeresource, and determining to preempt the first frequency-time resourceand transmit the uplink transmission based on satisfaction of thescheduling constraint.

A non-transitory computer-readable medium storing code for wirelesscommunication at a UE is described. The code may include instructionsexecutable by a processor to receive an uplink cancelation indicationfor a first frequency-time resource, receive, after receipt of theuplink cancelation indication, a grant for an uplink transmissionscheduled for transmission by the UE in a second frequency-timeresource, determine that the uplink transmission is scheduled so as tosatisfy a scheduling constraint that is based on whether the firstfrequency-time resource overlaps with the second frequency-timeresource, and determine to preempt the first frequency-time resource andtransmit the uplink transmission based on satisfaction of the schedulingconstraint.

In some examples of the method, apparatuses, and non-transitorycomputer-readable medium described herein, the scheduling constraint maybe satisfied based on the first frequency-time resource being entirelyseparate in time and frequency than the second frequency-time resource.

A method of wireless communication at a base station is described. Themethod may include transmitting a first grant for a first uplinktransmission scheduled for transmission by a UE, identifying that thefirst uplink transmission at least partially overlaps with a seconduplink transmission also scheduled for transmission by the UE,determining the second uplink transmission will be dropped by the UEbased on a first scheduling constraint to resolve overlapping betweenthe first uplink transmission and the second uplink transmission, wherethe first scheduling constraint is based at least in part on a firstpriority of the first uplink transmission being greater than a secondpriority of the second uplink transmission, and transmitting, after thefirst grant, an additional grant in accordance with a second schedulingconstraint, where the second scheduling constraint relates to anadditional uplink transmission scheduled by the additional grant andscheduled to at least partially overlap with the first uplinktransmission, and where the second scheduling constraint is evaluatedafter satisfaction of the first scheduling constraint to resolveoverlapping between the additional uplink transmission and the firstuplink transmission after resolving overlapping between the first uplinktransmission and the second uplink transmission.

An apparatus for wireless communication at a base station is described.The apparatus may include a processor, memory coupled with theprocessor, and instructions stored in the memory. The instructions maybe executable by the processor to cause the apparatus to transmit afirst grant for a first uplink transmission scheduled for transmissionby a UE, identify that the first uplink transmission at least partiallyoverlaps with a second uplink transmission also scheduled fortransmission by the UE, determine the second uplink transmission will bedropped by the UE based on a first scheduling constraint to resolveoverlapping between the first uplink transmission and the second uplinktransmission, where the first scheduling constraint is based at least inpart on a first priority of the first uplink transmission being greaterthan a second priority of the second uplink transmission, and transmit,after the first grant, an additional grant in accordance with a secondscheduling constraint, where the second scheduling constraint relates toan additional uplink transmission scheduled by the additional grant andscheduled to at least partially overlap with the first uplinktransmission, and where the second scheduling constraint is evaluatedafter satisfaction of the first scheduling constraint to resolveoverlapping between the additional uplink transmission and the firstuplink transmission after resolving overlapping between the first uplinktransmission and the second uplink transmission.

Another apparatus for wireless communication at a base station isdescribed. The apparatus may include means for transmitting a firstgrant for a first uplink transmission scheduled for transmission by aUE, identifying that the first uplink transmission at least partiallyoverlaps with a second uplink transmission also scheduled fortransmission by the UE, determining the second uplink transmission willbe dropped by the UE based on a first scheduling constraint to resolveoverlapping between the first uplink transmission and the second uplinktransmission, where the first scheduling constraint is based at least inpart on a first priority of the first uplink transmission being greaterthan a second priority of the second uplink transmission, andtransmitting, after the first grant, an additional grant in accordancewith a second scheduling constraint, where the second schedulingconstraint relates to an additional uplink transmission scheduled by theadditional grant and scheduled to at least partially overlap with thefirst uplink transmission, and where the second scheduling constraint isevaluated after satisfaction of the first scheduling constraint toresolve overlapping between the additional uplink transmission and thefirst uplink transmission after resolving overlapping between the firstuplink transmission and the second uplink transmission.

A non-transitory computer-readable medium storing code for wirelesscommunication at a base station is described. The code may includeinstructions executable by a processor to transmit a first grant for afirst uplink transmission scheduled for transmission by a UE, identifythat the first uplink transmission at least partially overlaps with asecond uplink transmission also scheduled for transmission by the UE,determine the second uplink transmission will be dropped by the UE basedon a first scheduling constraint to resolve overlapping between thefirst uplink transmission and the second uplink transmission, where thefirst scheduling constraint is based at least in part on a firstpriority of the first uplink transmission being greater than a secondpriority of the second uplink transmission, and transmit, after thefirst grant, an additional grant in accordance with a second schedulingconstraint, where the second scheduling constraint relates to anadditional uplink transmission scheduled by the additional grant andscheduled to at least partially overlap with the first uplinktransmission, and where the second scheduling constraint is evaluatedafter satisfaction of the first scheduling constraint to resolveoverlapping between the additional uplink transmission and the firstuplink transmission after resolving overlapping between the first uplinktransmission and the second uplink transmission.

Some examples of the method, apparatuses, and non-transitorycomputer-readable medium described herein may further includeoperations, features, means, or instructions for determining thetransmitted additional grant will be ignored by the UE based on thesecond scheduling constraint until overlapping between the first uplinktransmission and the second uplink transmission is resolved, where thesecond uplink transmission may be dropped based on the ignoring. Someexamples of the method, apparatuses, and non-transitorycomputer-readable medium described herein may further includeoperations, features, means, or instructions for determining the firstuplink transmission will be dropped by the UE based on transmitting theadditional grant. Some examples of the method, apparatuses, andnon-transitory computer-readable medium described herein may furtherinclude operations, features, means, or instructions for receiving theadditional uplink transmission and a piggybacked portion of the firstuplink transmission.

In some examples of the method, apparatuses, and non-transitorycomputer-readable medium described herein, the first uplink transmissionincludes a high priority uplink control channel transmission or a highpriority uplink shared channel transmission. In some examples of themethod, apparatuses, and non-transitory computer-readable mediumdescribed herein, the second uplink transmission includes a low priorityuplink control channel transmission, a low priority uplink sharedchannel transmission, or a sounding reference signal transmission. Insome examples of the method, apparatuses, and non-transitorycomputer-readable medium described herein, the additional uplinktransmission includes an additional high priority uplink transmission.In some examples of the method, apparatuses, and non-transitorycomputer-readable medium described herein, the additional grant includesa group-common grant, an uplink cancelation indication, or a slot formatindicator.

A method of wireless communication at a base station is described. Themethod may include identifying that a first uplink transmissionscheduled for transmission by a UE at least partially overlaps with asecond uplink transmission also scheduled for transmission by the UE,transmitting an uplink cancelation indication for a frequency-timeresource that at least partially overlaps with the first uplinktransmission, the second uplink transmission, or both, determining thesecond uplink transmission will be dropped by the UE based on a firstscheduling constraint to resolve overlapping between the first uplinktransmission and the second uplink transmission, where the firstscheduling constraint is based at least in part on a first priority ofthe first uplink transmission being greater than a second priority ofthe second uplink transmission, and receiving the first uplinktransmission in accordance with a second scheduling constraint, wherethe second scheduling constraint is evaluated after satisfaction of thefirst scheduling constraint, and where the second scheduling constraintrelates to the frequency-time resource at least partially overlappingwith the first uplink transmission, the second uplink transmission, orboth.

An apparatus for wireless communication at a base station is described.The apparatus may include a processor, memory coupled with theprocessor, and instructions stored in the memory. The instructions maybe executable by the processor to cause the apparatus to identify that afirst uplink transmission scheduled for transmission by a UE at leastpartially overlaps with a second uplink transmission also scheduled fortransmission by the UE, transmit an uplink cancelation indication for afrequency-time resource that at least partially overlaps with the firstuplink transmission, the second uplink transmission, or both, determinethe second uplink transmission will be dropped by the UE based on afirst scheduling constraint to resolve overlapping between the firstuplink transmission and the second uplink transmission, where the firstscheduling constraint is based at least in part on a first priority ofthe first uplink transmission being greater than a second priority ofthe second uplink transmission, and receive the first uplinktransmission in accordance with a second scheduling constraint, wherethe second scheduling constraint is evaluated after satisfaction of thefirst scheduling constraint, and where the second scheduling constraintrelates to the frequency-time resource at least partially overlappingwith the first uplink transmission, the second uplink transmission, orboth.

Another apparatus for wireless communication at a base station isdescribed. The apparatus may include means for identifying that a firstuplink transmission scheduled for transmission by a UE at leastpartially overlaps with a second uplink transmission also scheduled fortransmission by the UE, transmitting an uplink cancelation indicationfor a frequency-time resource that at least partially overlaps with thefirst uplink transmission, the second uplink transmission, or both,determining the second uplink transmission will be dropped by the UEbased on a first scheduling constraint to resolve overlapping betweenthe first uplink transmission and the second uplink transmission, wherethe first scheduling constraint is based at least in part on a firstpriority of the first uplink transmission being greater than a secondpriority of the second uplink transmission, and receiving the firstuplink transmission in accordance with a second scheduling constraint,where the second scheduling constraint is evaluated after satisfactionof the first scheduling constraint, and where the second schedulingconstraint relates to the frequency-time resource at least partiallyoverlapping with the first uplink transmission, the second uplinktransmission, or both.

A non-transitory computer-readable medium storing code for wirelesscommunication at a base station is described. The code may includeinstructions executable by a processor to identify that a first uplinktransmission scheduled for transmission by a UE at least partiallyoverlaps with a second uplink transmission also scheduled fortransmission by the UE, transmit an uplink cancelation indication for afrequency-time resource that at least partially overlaps with the firstuplink transmission, the second uplink transmission, or both, determinethe second uplink transmission will be dropped by the UE based on afirst scheduling constraint to resolve overlapping between the firstuplink transmission and the second uplink transmission, where the firstscheduling constraint is based at least in part on a first priority ofthe first uplink transmission being greater than a second priority ofthe second uplink transmission, and receive the first uplinktransmission in accordance with a second scheduling constraint, wherethe second scheduling constraint is evaluated after satisfaction of thefirst scheduling constraint, and where the second scheduling constraintrelates to the frequency-time resource at least partially overlappingwith the first uplink transmission, the second uplink transmission, orboth.

In some examples of the method, apparatuses, and non-transitorycomputer-readable medium described herein, receiving the first uplinktransmission in accordance with the second scheduling constraint mayinclude operations, features, means, or instructions for determining thefirst uplink transmission will be dropped by the UE based on thefrequency-time resource at least partially overlapping with the firstuplink transmission. In some examples of the method, apparatuses, andnon-transitory computer-readable medium described herein, receiving thefirst uplink transmission in accordance with the second schedulingconstraint may include operations, features, means, or instructions forreceiving the first uplink transmission based on the frequency-timeresource at least partially overlapping with the second uplinktransmission.

In some examples of the method, apparatuses, and non-transitorycomputer-readable medium described herein, the first uplink transmissionincludes a high priority uplink control channel transmission or a highpriority uplink shared channel transmission. In some examples of themethod, apparatuses, and non-transitory computer-readable mediumdescribed herein, the second uplink transmission includes a low priorityuplink control channel transmission, a low priority uplink sharedchannel transmission, or a sounding reference signal transmission.

A method of wireless communication at a base station is described. Themethod may include transmitting a first grant for a first uplinktransmission scheduled for transmission by a UE, identifying ascheduling constraint based on a first priority of the first uplinktransmission being greater than a second priority of a second uplinktransmission to be scheduled by a second grant transmitted after thefirst grant, and transmitting, after the first grant, the second grantin accordance with the scheduling constraint.

An apparatus for wireless communication at a base station is described.The apparatus may include a processor, memory coupled with theprocessor, and instructions stored in the memory. The instructions maybe executable by the processor to cause the apparatus to transmit afirst grant for a first uplink transmission scheduled for transmissionby a UE, identify a scheduling constraint based on a first priority ofthe first uplink transmission being greater than a second priority of asecond uplink transmission to be scheduled by a second grant transmittedafter the first grant, and transmit, after the first grant, the secondgrant in accordance with the scheduling constraint.

Another apparatus for wireless communication at a base station isdescribed. The apparatus may include means for transmitting a firstgrant for a first uplink transmission scheduled for transmission by aUE, identifying a scheduling constraint based on a first priority of thefirst uplink transmission being greater than a second priority of asecond uplink transmission to be scheduled by a second grant transmittedafter the first grant, and transmitting, after the first grant, thesecond grant in accordance with the scheduling constraint.

A non-transitory computer-readable medium storing code for wirelesscommunication at a base station is described. The code may includeinstructions executable by a processor to transmit a first grant for afirst uplink transmission scheduled for transmission by a UE, identify ascheduling constraint based on a first priority of the first uplinktransmission being greater than a second priority of a second uplinktransmission to be scheduled by a second grant transmitted after thefirst grant, and transmit, after the first grant, the second grant inaccordance with the scheduling constraint.

Some examples of the method, apparatuses, and non-transitorycomputer-readable medium described herein may further includeoperations, features, means, or instructions for receiving the firstuplink transmission based on the transmitted first grant. In someexamples of the method, apparatuses, and non-transitorycomputer-readable medium described herein, the first grant includes adynamic high priority grant. Some examples of the method, apparatuses,and non-transitory computer-readable medium described herein may furtherinclude operations, features, means, or instructions for receiving thesecond uplink transmission based on the transmitted additional grant. Insome examples of the method, apparatuses, and non-transitorycomputer-readable medium described herein, the first uplink transmissionincludes a high priority scheduling request or a high priority uplinkconfigured grant transmission.

Some examples of the method, apparatuses, and non-transitorycomputer-readable medium described herein may further includeoperations, features, means, or instructions for determining the UEskipped the first uplink transmission based on receiving the seconduplink transmission, where the determination that the UE skipped thefirst uplink transmission may be based on a buffer status of the UEbeing below a threshold. In some examples of the method, apparatuses,and non-transitory computer-readable medium described herein, thescheduling constraint further relates to the second uplink transmissionscheduled to overlap with the first uplink transmission.

In some examples of the method, apparatuses, and non-transitorycomputer-readable medium described herein, the first uplink transmissioncomprises a hybrid automatic repeat request acknowledgment transmissionor a channel state information transmission. In some examples of themethod, apparatuses, and non-transitory computer-readable mediumdescribed herein, the scheduling constraint provides that the UE doesnot expect to receive a grant scheduling a low priority uplinktransmission that overlaps with a previously scheduled high priorityuplink transmission.

A method of wireless communication at a base station is described. Themethod may include transmitting, to a UE, an uplink cancelationindication for a first frequency-time resource, identifying a schedulingconstraint that is based on whether the first frequency-time resourceoverlaps with a second frequency-time resource of an uplink transmissionto be scheduled by a grant, and transmitting, after transmission of theuplink cancelation indication, the grant for the uplink transmission inaccordance with the scheduling constraint.

An apparatus for wireless communication at a base station is described.The apparatus may include a processor, memory coupled with theprocessor, and instructions stored in the memory. The instructions maybe executable by the processor to cause the apparatus to transmit, to aUE, an uplink cancelation indication for a first frequency-timeresource, identify a scheduling constraint that is based on whether thefirst frequency-time resource overlaps with a second frequency-timeresource of an uplink transmission to be scheduled by a grant, andtransmit, after transmission of the uplink cancelation indication, thegrant for the uplink transmission in accordance with the schedulingconstraint.

Another apparatus for wireless communication at a base station isdescribed. The apparatus may include means for transmitting, to a UE, anuplink cancelation indication for a first frequency-time resource,identifying a scheduling constraint that is based on whether the firstfrequency-time resource overlaps with a second frequency-time resourceof an uplink transmission to be scheduled by a grant, and transmitting,after transmission of the uplink cancelation indication, the grant forthe uplink transmission in accordance with the scheduling constraint.

A non-transitory computer-readable medium storing code for wirelesscommunication at a base station is described. The code may includeinstructions executable by a processor to transmit, to a UE, an uplinkcancelation indication for a first frequency-time resource, identify ascheduling constraint that is based on whether the first frequency-timeresource overlaps with a second frequency-time resource of an uplinktransmission to be scheduled by a grant, and transmit, aftertransmission of the uplink cancelation indication, the grant for theuplink transmission in accordance with the scheduling constraint.

In some examples of the method, apparatuses, and non-transitorycomputer-readable medium described herein, the scheduling constraint maybe satisfied based on the first frequency-time resource being entirelyseparate in time and frequency than the second frequency-time resource.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 illustrates an example of a wireless communications system thatsupports techniques for intra-user equipment (UE) and inter-UEcancelation of overlapping communications in accordance with aspects ofthe present disclosure.

FIG. 2 illustrates an example of a wireless communications system thatsupports techniques for intra-UE and inter-UE cancelation of overlappingcommunications in accordance with aspects of the present disclosure.

FIGS. 3A and 3B illustrate example scheduling diagrams that supporttechniques for intra-UE and inter-UE cancelation of overlappingcommunications in accordance with aspects of the present disclosure.

FIG. 4 illustrates an example of a scheduling diagram that supportstechniques for intra-UE and inter-UE cancelation of overlappingcommunications in accordance with aspects of the present disclosure.

FIGS. 5A and 5B illustrate example scheduling diagrams that supporttechniques for intra-UE and inter-UE cancelation of overlappingcommunications in accordance with aspects of the present disclosure.

FIG. 6 illustrates an example of a process flow that supports techniquesfor intra-UE and inter-UE cancelation of overlapping communications inaccordance with aspects of the present disclosure.

FIGS. 7 and 8 show block diagrams of devices that support techniques forintra-UE and inter-UE cancelation of overlapping communications inaccordance with aspects of the present disclosure.

FIG. 9 shows a block diagram of a communications manager that supportstechniques for intra-UE and inter-UE cancelation of overlappingcommunications in accordance with aspects of the present disclosure.

FIG. 10 shows a diagram of a system including a device that supportstechniques for intra-UE and inter-UE cancelation of overlappingcommunications in accordance with aspects of the present disclosure.

FIGS. 11 and 12 show block diagrams of devices that support techniquesfor intra-UE and inter-UE cancelation of overlapping communications inaccordance with aspects of the present disclosure.

FIG. 13 shows a block diagram of a communications manager that supportstechniques for intra-UE and inter-UE cancelation of overlappingcommunications in accordance with aspects of the present disclosure.

FIG. 14 shows a diagram of a system including a device that supportstechniques for intra-UE and inter-UE cancelation of overlappingcommunications in accordance with aspects of the present disclosure.

FIGS. 15 through 22 show flowcharts illustrating methods that supporttechniques for intra-UE and inter-UE cancelation of overlappingcommunications in accordance with aspects of the present disclosure.

DETAILED DESCRIPTION

Some communication systems may support different traffic types (e.g.,traffic categories), which may include or refer to communicationstraffic having different reliability thresholds, different latencythresholds, different services, or various combinations thereof. Forexample, a wireless communication system may support a first traffictype (e.g., communications type), associated with relatively highreliability targets or thresholds and relatively low latency targets orthresholds, such as an ultra-reliable low-latency communications (URLLC)traffic type. The wireless communication system may also support asecond traffic type, associated with relatively low reliability targetsor thresholds and relatively long or relaxed latency thresholds, such asan enhanced mobile broadband (eMBB) traffic type. In some cases, tosupport various system operations (e.g., efficient utilization ofwireless communication resources, appropriate allocation or balancing ofwireless communication resources, or appropriate support of trafficaccording to different prioritizations or latency thresholds), awireless communication system may support dynamic resource sharingbetween traffic types, such as a dynamic allocation of resources betweenURLLC communications and eMBB communications, or other communications,according to different traffic types, categories, or otherprioritizations.

Generally, techniques for dynamic resource allocation may includecancelation, preemption, or repurposing of previously-allocated uplinkresources by a network entity (e.g., such as a base station or othercontroller or resource allocation authority in communication with a basestation). For example, a base station, or other network entity, mayallocate or schedule uplink resources (e.g., an initial uplink resourceallocation via an initial grant) to UEs, or groups of UEs, and the basestation may subsequently reclaim or repurpose the scheduled uplinkresources. In order to support such dynamic resource sharing, wirelesscommunications systems may support intra-UE multiplexing and cancelationrules in addition to inter-UE multiplexing and cancelation rules.

For instance, intra-UE multiplexing and cancelation rules may includetechniques for UE handling of uplink transmissions, scheduled for theUE, that overlap in time (e.g., such techniques may include uplinkcontrol information (UCI) piggybacking, periodic channel stateinformation (P-CSI) dropping, etc.). For example, if a physical uplinkcontrol channel (PUCCH) carrying hybrid automatic repeat request (HARQ)feedback scheduled for the UE overlaps with a physical uplink sharedchannel (PUSCH) scheduled for the UE, the UE may follow intra-UEmultiplexing and cancelation rules. If the two overlapping (e.g.,colliding) uplink transmissions are of a same priority, the UE maymultiplex the PUCCH with the PUSCH (e.g., the UCI of the PUCCH may bepiggybacked onto the PUSCH, and the PUSCH may be transmitted). However,if the two overlapping transmissions are of different priorities (e.g.,if a high priority PUSCH and a low priority PUSCH overlap), the lowerpriority uplink transmission may be dropped.

Inter-UE multiplexing and cancelation rules may include techniques forbase station handling of uplink transmissions, scheduled for differentUEs, that overlap in time (e.g., such techniques may include using anuplink preemption indication (ULPI) or a downlink preemption indication(DLPI) that may correspond to at least a portion of previously-allocateduplink or downlink resources). For example, a base station may allocateuplink resources (e.g., an initial uplink resource allocation) to a UE,and the base station may subsequently issue a preemption indication(e.g., an ULPI or a DLPI) to reclaim or reallocate at least a portion ofthe previously-allocated uplink resources. UEs may detect such apreemption indication and determine whether or not to proceed with anuplink transmission using their previously-allocated uplink resources(e.g., based on whether or not the preemption indication is directed tothe UE, based on resources indicated by the ULPI, etc.). In someexamples, a preemption indication may be used to prevent a UE from usingat least a portion of previously-allocated uplink resources for anuplink transmission. For example, resources that were originallyallocated to one UE for eMBB communications may be reallocated toanother UE for URLLC communications (e.g., a reallocation towards moreperformance-sensitive communications).

However, in some scenarios, such techniques for dynamic resourceallocation may be ambiguous or otherwise deficient. As an example, a UEmay receive a first grant (e.g., for a low priority PUSCH) followed by asecond grant (e.g., for a high priority PUCCH) and, in accordance withthe rules mentioned above, the UE may decide to drop one of thescheduled transmissions (e.g., the low priority PUSCH scheduled by thefirst grant). However, it is also possible that the UE may receive athird grant (e.g., for a high priority PUSCH) which might allow for thepreviously scheduled high priority PUCCH to be multiplexed with thenewly scheduled high priority PUSCH. In so doing, the third grant mayremove the condition which caused the UE to elect to drop the lowpriority PUSCH. For instance, when the high priority PUCCH ispiggybacked on the high priority PUSCH, the high priority PUCCH (e.g.,which initially caused the UE to determine to drop the low priorityPUSCH) may no longer overlap with the low priority PUSCH (e.g., as theUCI of the high priority PUCCH may be piggybacked onto the high priorityPUSCH, and the high priority PUSCH may be associated with differentresources than the resources of the high priority PUCCH that overlappedwith the dropped, low priority PUSCH).

As such, the techniques described herein may provide for one or morescheduling constraints to support efficient utilization of dynamicresource allocation (e.g., to support efficient intra-UE and inter-UEhandling of overlapping scheduled transmissions). For example, thedescribed techniques may provide for scheduling constraints that maydefine how a UE may apply intra-UE and inter-UE multiplexing andcancelation rules in various scenarios. For example, a UE may applyintra-UE cancelation rules (e.g., potentially resulting in a droppeduplink transmission) before inter-UE cancelation rules. In someexamples, later-received grants or later-received ULPIs may not change aUE's decision to drop an uplink transmission. As another example of ascheduling constraint, a UE may not expect to receive a grant for anuplink transmission that would arise in subsequent cancelation of thatuplink transmission due to a previously-received grant orpreviously-received ULPI.

Thus, according to these and other examples, various uplink resourceallocations may be unambiguously canceled, preempted, or reallocated,thereby supporting efficient dynamic allocation, preemption, andredistribution of uplink resources in a wireless communication systemthat more-effectively balances the performance and resource utilizationof communications according to different priorities. Such may providefor more efficient resource utilization and resource reallocation withinwireless communications systems supporting various different servicedeployments. Further, the described techniques (e.g., the describedscheduling constraints) may provide for reduced computational complexityat the UE (e.g., due to the alleviated handling of ambiguous scenarioswhere a UE may otherwise transition back and forth betweendeterminations of whether to cancel or perform an uplink transmission).

Aspects of the disclosure are initially described in the context ofwireless communications systems. Example scheduling diagrams and anexample process flow illustrating aspects of the discussed techniquesand then described. Aspects of the disclosure are further illustrated byand described with reference to apparatus diagrams, system diagrams, andflowcharts that relate to techniques for intra-UE and inter-UEcancelation of overlapping communications.

FIG. 1 illustrates an example of a wireless communications system 100that supports techniques for intra-UE and inter-UE cancelation ofoverlapping communications in accordance with aspects of the presentdisclosure. The wireless communications system 100 may include one ormore base stations 105, one or more UEs 115, and a core network 130. Insome examples, the wireless communications system 100 may be a Long-TermEvolution (LTE) network, an LTE-Advanced (LTE-A) network, an LTE-A Pronetwork, or a New Radio (NR) network. In some examples, the wirelesscommunications system 100 may support enhanced broadband communications,ultra-reliable (e.g., mission critical) communications, low latencycommunications, communications with low-cost and low-complexity devices,or any combination thereof.

The base stations 105 may be dispersed throughout a geographic area toform the wireless communications system 100 and may be devices indifferent forms or having different capabilities. The base stations 105and the UEs 115 may wirelessly communicate via one or more communicationlinks 125. Each base station 105 may provide a coverage area 110 overwhich the UEs 115 and the base station 105 may establish one or morecommunication links 125. The coverage area 110 may be an example of ageographic area over which a base station 105 and a UE 115 may supportthe communication of signals according to one or more radio accesstechnologies.

The UEs 115 may be dispersed throughout a coverage area 110 of thewireless communications system 100, and each UE 115 may be stationary,or mobile, or both at different times. The UEs 115 may be devices indifferent forms or having different capabilities. Some example UEs 115are illustrated in FIG. 1 . The UEs 115 described herein may be able tocommunicate with various types of devices, such as other UEs 115, thebase stations 105, or network equipment (e.g., core network nodes, relaydevices, integrated access and backhaul (IAB) nodes, or other networkequipment), as shown in FIG. 1 .

The base stations 105 may communicate with the core network 130, or withone another, or both. For example, the base stations 105 may interfacewith the core network 130 through one or more backhaul links 120 (e.g.,via an S1, N2, N3, or other interface). The base stations 105 maycommunicate with one another over the backhaul links 120 (e.g., via anX2, Xn, or other interface) either directly (e.g., directly between basestations 105), or indirectly (e.g., via core network 130), or both. Insome examples, the backhaul links 120 may be or include one or morewireless links.

One or more of the base stations 105 described herein may include or maybe referred to by a person having ordinary skill in the art as a basetransceiver station, a radio base station, an access point, a radiotransceiver, a NodeB, an eNodeB (eNB), a next-generation NodeB or agiga-NodeB (either of which may be referred to as a gNB), a Home NodeB,a Home eNodeB, or other suitable terminology.

A UE 115 may include or may be referred to as a mobile device, awireless device, a remote device, a handheld device, or a subscriberdevice, or some other suitable terminology, where the “device” may alsobe referred to as a unit, a station, a terminal, or a client, amongother examples. A UE 115 may also include or may be referred to as apersonal electronic device such as a cellular phone, a personal digitalassistant (PDA), a tablet computer, a laptop computer, or a personalcomputer. In some examples, a UE 115 may include or be referred to as awireless local loop (WLL) station, an Internet of Things (IoT) device,an Internet of Everything (IoE) device, or a machine type communications(MTC) device, among other examples, which may be implemented in variousobjects such as appliances, or vehicles, meters, among other examples.

The UEs 115 described herein may be able to communicate with varioustypes of devices, such as other UEs 115 that may sometimes act as relaysas well as the base stations 105 and the network equipment includingmacro eNBs or gNBs, small cell eNBs or gNBs, or relay base stations,among other examples, as shown in FIG. 1 .

The UEs 115 and the base stations 105 may wirelessly communicate withone another via one or more communication links 125 over one or morecarriers. The term “carrier” may refer to a set of radio frequencyspectrum resources having a defined physical layer structure forsupporting the communication links 125. For example, a carrier used fora communication link 125 may include a portion of a radio frequencyspectrum band (e.g., a bandwidth part (BWP)) that is operated accordingto one or more physical layer channels for a given radio accesstechnology (e.g., LTE, LTE-A, LTE-A Pro, NR). Each physical layerchannel may carry acquisition signaling (e.g., synchronization signals,system information), control signaling that coordinates operation forthe carrier, user data, or other signaling. The wireless communicationssystem 100 may support communication with a UE 115 using carrieraggregation or multi-carrier operation. A UE 115 may be configured withmultiple downlink component carriers and one or more uplink componentcarriers according to a carrier aggregation configuration. Carrieraggregation may be used with both frequency division duplexing (FDD) andtime division duplexing (TDD) component carriers.

In some examples (e.g., in a carrier aggregation configuration), acarrier may also have acquisition signaling or control signaling thatcoordinates operations for other carriers. A carrier may be associatedwith a frequency channel (e.g., an evolved universal mobiletelecommunication system terrestrial radio access (E-UTRA) absoluteradio frequency channel number (EARFCN)) and may be positioned accordingto a channel raster for discovery by the UEs 115. A carrier may beoperated in a standalone mode where initial acquisition and connectionmay be conducted by the UEs 115 via the carrier, or the carrier may beoperated in a non-standalone mode where a connection is anchored using adifferent carrier (e.g., of the same or a different radio accesstechnology).

The communication links 125 shown in the wireless communications system100 may include uplink transmissions from a UE 115 to a base station105, or downlink transmissions from a base station 105 to a UE 115.Carriers may carry downlink or uplink communications (e.g., in an FDDmode) or may be configured to carry downlink and uplink communications(e.g., in a TDD mode).

A carrier may be associated with a particular bandwidth of the radiofrequency spectrum, and in some examples the carrier bandwidth may bereferred to as a “system bandwidth” of the carrier or the wirelesscommunications system 100. For example, the carrier bandwidth may be oneof a number of determined bandwidths for carriers of a particular radioaccess technology (e.g., 1.4, 3, 5, 10, 15, 20, 40, or 80 megahertz(MHz)). Devices of the wireless communications system 100 (e.g., thebase stations 105, the UEs 115, or both) may have hardwareconfigurations that support communications over a particular carrierbandwidth or may be configurable to support communications over one of aset of carrier bandwidths. In some examples, the wireless communicationssystem 100 may include base stations 105 or UEs 115 that supportsimultaneous communications via carriers associated with multiplecarrier bandwidths. In some examples, each served UE 115 may beconfigured for operating over portions (e.g., a sub-band, a BWP) or allof a carrier bandwidth.

Signal waveforms transmitted over a carrier may be made up of multiplesubcarriers (e.g., using multi-carrier modulation (MCM) techniques suchas orthogonal frequency division multiplexing (OFDM) or discrete Fouriertransform spread OFDM (DFT-S-OFDM)). In a system employing MCMtechniques, a resource element may consist of one symbol period (e.g., aduration of one modulation symbol) and one subcarrier, where the symbolperiod and subcarrier spacing are inversely related. The number of bitscarried by each resource element may depend on the modulation scheme(e.g., the order of the modulation scheme, the coding rate of themodulation scheme, or both). Thus, the more resource elements that a UE115 receives and the higher the order of the modulation scheme, thehigher the data rate may be for the UE 115. A wireless communicationsresource may refer to a combination of a radio frequency spectrumresource, a time resource, and a spatial resource (e.g., spatial layersor beams), and the use of multiple spatial layers may further increasethe data rate or data integrity for communications with a UE 115.

One or more numerologies for a carrier may be supported, where anumerology may include a subcarrier spacing (Δf) and a cyclic prefix. Acarrier may be divided into one or more BWPs having the same ordifferent numerologies. In some examples, a UE 115 may be configuredwith multiple BWPs. In some examples, a single BWP for a carrier may beactive at a given time and communications for the UE 115 may berestricted to one or more active BWPs.

The time intervals for the base stations 105 or the UEs 115 may beexpressed in multiples of a basic time unit which may, for example,refer to a sampling period of T_s=1/((Δf_max·N_f)) seconds, where Δf_maxmay represent the maximum supported subcarrier spacing, and N_f mayrepresent the maximum supported discrete Fourier transform (DFT) size.Time intervals of a communications resource may be organized accordingto radio frames each having a specified duration (e.g., 10 milliseconds(ms)). Each radio frame may be identified by a system frame number (SFN)(e.g., ranging from 0 to 1023).

Each frame may include multiple consecutively numbered subframes orslots, and each subframe or slot may have the same duration. In someexamples, a frame may be divided (e.g., in the time domain) intosubframes, and each subframe may be further divided into a number ofslots. Alternatively, each frame may include a variable number of slots,and the number of slots may depend on subcarrier spacing. Each slot mayinclude a number of symbol periods (e.g., depending on the length of thecyclic prefix prepended to each symbol period). In some wirelesscommunications systems 100, a slot may further be divided into multiplemini-slots containing one or more symbols. Excluding the cyclic prefix,each symbol period may contain one or more (e.g., N_f) sampling periods.The duration of a symbol period may depend on the subcarrier spacing orfrequency band of operation.

A subframe, a slot, a mini-slot, or a symbol may be the smallestscheduling unit (e.g., in the time domain) of the wirelesscommunications system 100 and may be referred to as a transmission timeinterval (TTI). In some examples, the TTI duration (e.g., the number ofsymbol periods in a TTI) may be variable. Additionally, oralternatively, the smallest scheduling unit of the wirelesscommunications system 100 may be dynamically selected (e.g., in burstsof shortened TTIs (sTTIs)).

Physical channels may be multiplexed on a carrier according to varioustechniques. A physical control channel and a physical data channel maybe multiplexed on a downlink carrier, for example, using one or more oftime division multiplexing (TDM) techniques, frequency divisionmultiplexing (FDM) techniques, or hybrid TDM-FDM techniques. A controlregion (e.g., a control resource set (CORESET)) for a physical controlchannel may be defined by a number of symbol periods and may extendacross the system bandwidth or a subset of the system bandwidth of thecarrier. One or more control regions (e.g., CORESETs) may be configuredfor a set of the UEs 115. For example, one or more of the UEs 115 maymonitor or search control regions for control information according toone or more search space sets, and each search space set may include oneor multiple control channel candidates in one or more aggregation levelsarranged in a cascaded manner. An aggregation level for a controlchannel candidate may refer to a number of control channel resources(e.g., control channel elements (CCEs)) associated with encodedinformation for a control information format having a given payloadsize. Search space sets may include common search space sets configuredfor sending control information to multiple UEs 115 and UE-specificsearch space sets for sending control information to a specific UE 115.

Each base station 105 may provide communication coverage via one or morecells, for example a macro cell, a small cell, a hot spot, or othertypes of cells, or any combination thereof. The term “cell” may refer toa logical communication entity used for communication with a basestation 105 (e.g., over a carrier) and may be associated with anidentifier for distinguishing neighboring cells (e.g., a physical cellidentifier (PCID), a virtual cell identifier (VCID), or others). In someexamples, a cell may also refer to a geographic coverage area 110 or aportion of a geographic coverage area 110 (e.g., a sector) over whichthe logical communication entity operates. Such cells may range fromsmaller areas (e.g., a structure, a subset of structure) to larger areasdepending on various factors such as the capabilities of the basestation 105. For example, a cell may be or include a building, a subsetof a building, or exterior spaces between or overlapping with geographiccoverage areas 110, among other examples.

A macro cell generally covers a relatively large geographic area (e.g.,several kilometers in radius) and may allow unrestricted access by theUEs 115 with service subscriptions with the network provider supportingthe macro cell. A small cell may be associated with a lower-powered basestation 105, as compared with a macro cell, and a small cell may operatein the same or different (e.g., licensed, unlicensed) frequency bands asmacro cells. Small cells may provide unrestricted access to the UEs 115with service subscriptions with the network provider or may providerestricted access to the UEs 115 having an association with the smallcell (e.g., the UEs 115 in a closed subscriber group (CSG), the UEs 115associated with users in a home or office). A base station 105 maysupport one or multiple cells and may also support communications overthe one or more cells using one or multiple component carriers.

In some examples, a carrier may support multiple cells, and differentcells may be configured according to different protocol types (e.g.,MTC, narrowband IoT (NB-IoT), enhanced mobile broadband (eMBB)) that mayprovide access for different types of devices.

In some examples, a base station 105 may be movable and thereforeprovide communication coverage for a moving geographic coverage area110. In some examples, different geographic coverage areas 110associated with different technologies may overlap, but the differentgeographic coverage areas 110 may be supported by the same base station105. In other examples, the overlapping geographic coverage areas 110associated with different technologies may be supported by differentbase stations 105. The wireless communications system 100 may include,for example, a heterogeneous network in which different types of thebase stations 105 provide coverage for various geographic coverage areas110 using the same or different radio access technologies.

The wireless communications system 100 may support synchronous orasynchronous operation. For synchronous operation, the base stations 105may have similar frame timings, and transmissions from different basestations 105 may be approximately aligned in time. For asynchronousoperation, the base stations 105 may have different frame timings, andtransmissions from different base stations 105 may, in some examples,not be aligned in time. The techniques described herein may be used foreither synchronous or asynchronous operations.

Some UEs 115, such as MTC or IoT devices, may be low cost or lowcomplexity devices and may provide for automated communication betweenmachines (e.g., via Machine-to-Machine (M2M) communication). M2Mcommunication or MTC may refer to data communication technologies thatallow devices to communicate with one another or a base station 105without human intervention. In some examples, M2M communication or MTCmay include communications from devices that integrate sensors or metersto measure or capture information and relay such information to acentral server or application program that makes use of the informationor presents the information to humans interacting with the applicationprogram. Some UEs 115 may be designed to collect information or enableautomated behavior of machines or other devices. Examples ofapplications for MTC devices include smart metering, inventorymonitoring, water level monitoring, equipment monitoring, healthcaremonitoring, wildlife monitoring, weather and geological eventmonitoring, fleet management and tracking, remote security sensing,physical access control, and transaction-based business charging.

Some UEs 115 may be configured to employ operating modes that reducepower consumption, such as half-duplex communications (e.g., a mode thatsupports one-way communication via transmission or reception, but nottransmission and reception simultaneously). In some examples,half-duplex communications may be performed at a reduced peak rate.Other power conservation techniques for the UEs 115 include entering apower saving deep sleep mode when not engaging in active communications,operating over a limited bandwidth (e.g., according to narrowbandcommunications), or a combination of these techniques. For example, someUEs 115 may be configured for operation using a narrowband protocol typethat is associated with a defined portion or range (e.g., set ofsubcarriers or resource blocks (RBs)) within a carrier, within aguard-band of a carrier, or outside of a carrier.

The wireless communications system 100 may be configured to supportultra-reliable communications or low-latency communications, or variouscombinations thereof. For example, the wireless communications system100 may be configured to support ultra-reliable low-latencycommunications (URLLC) or mission critical communications. The UEs 115may be designed to support ultra-reliable, low-latency, or criticalfunctions (e.g., mission critical functions). Ultra-reliablecommunications may include private communication or group communicationand may be supported by one or more mission critical services such asmission critical push-to-talk (MCPTT), mission critical video (MCVideo),or mission critical data (MCData). Support for mission criticalfunctions may include prioritization of services, and mission criticalservices may be used for public safety or general commercialapplications. The terms ultra-reliable, low-latency, mission critical,and ultra-reliable low-latency may be used interchangeably herein.

In some examples, a UE 115 may also be able to communicate directly withother UEs 115 over a device-to-device (D2D) communication link 135(e.g., using a peer-to-peer (P2P) or D2D protocol). One or more UEs 115utilizing D2D communications may be within the geographic coverage area110 of a base station 105. Other UEs 115 in such a group may be outsidethe geographic coverage area 110 of a base station 105 or be otherwiseunable to receive transmissions from a base station 105. In someexamples, groups of the UEs 115 communicating via D2D communications mayutilize a one-to-many (1:M) system in which each UE 115 transmits toevery other UE 115 in the group. In some examples, a base station 105facilitates the scheduling of resources for D2D communications. In othercases, D2D communications are carried out between the UEs 115 withoutthe involvement of a base station 105.

In some systems, the D2D communication link 135 may be an example of acommunication channel, such as a sidelink communication channel, betweenvehicles (e.g., UEs 115). In some examples, vehicles may communicateusing vehicle-to-everything (V2X) communications, vehicle-to-vehicle(V2V) communications, or some combination of these. A vehicle may signalinformation related to traffic conditions, signal scheduling, weather,safety, emergencies, or any other information relevant to a V2X system.In some examples, vehicles in a V2X system may communicate with roadsideinfrastructure, such as roadside units, or with the network via one ormore network nodes (e.g., base stations 105) using vehicle-to-network(V2N) communications, or with both.

The core network 130 may provide user authentication, accessauthorization, tracking, Internet Protocol (IP) connectivity, and otheraccess, routing, or mobility functions. The core network 130 may be anevolved packet core (EPC) or 5G core (5GC), which may include at leastone control plane entity that manages access and mobility (e.g., amobility management entity (MME), an access and mobility managementfunction (AMF)) and at least one user plane entity that routes packetsor interconnects to external networks (e.g., a serving gateway (S-GW), aPacket Data Network (PDN) gateway (P-GW), or a user plane function(UPF)). The control plane entity may manage non-access stratum (NAS)functions such as mobility, authentication, and bearer management forthe UEs 115 served by the base stations 105 associated with the corenetwork 130. User IP packets may be transferred through the user planeentity, which may provide IP address allocation as well as otherfunctions. The user plane entity may be connected to the networkoperators IP services 150. The operators IP services 150 may includeaccess to the Internet, Intranet(s), an IP Multimedia Subsystem (IMS),or a Packet-Switched Streaming Service.

Some of the network devices, such as a base station 105, may includesubcomponents such as an access network entity 140, which may be anexample of an access node controller (ANC). Each access network entity140 may communicate with the UEs 115 through one or more other accessnetwork transmission entities 145, which may be referred to as radioheads, smart radio heads, or transmission/reception points (TRPs). Eachaccess network transmission entity 145 may include one or more antennapanels. In some configurations, various functions of each access networkentity 140 or base station 105 may be distributed across various networkdevices (e.g., radio heads and ANCs) or consolidated into a singlenetwork device (e.g., a base station 105).

The wireless communications system 100 may operate using one or morefrequency bands, typically in the range of 300 megahertz (MHz) to 300gigahertz (GHz). Generally, the region from 300 MHz to 3 GHz is known asthe ultra-high frequency (UHF) region or decimeter band because thewavelengths range from approximately one decimeter to one meter inlength. The UHF waves may be blocked or redirected by buildings andenvironmental features, but the waves may penetrate structuressufficiently for a macro cell to provide service to the UEs 115 locatedindoors. The transmission of UHF waves may be associated with smallerantennas and shorter ranges (e.g., less than 100 kilometers) compared totransmission using the smaller frequencies and longer waves of the highfrequency (HF) or very high frequency (VHF) portion of the spectrumbelow 300 MHz.

The wireless communications system 100 may also operate in a super highfrequency (SHF) region using frequency bands from 3 GHz to 30 GHz, alsoknown as the centimeter band, or in an extremely high frequency (EHF)region of the spectrum (e.g., from 30 GHz to 300 GHz), also known as themillimeter band. In some examples, the wireless communications system100 may support millimeter wave (mmW) communications between the UEs 115and the base stations 105, and EHF antennas of the respective devicesmay be smaller and more closely spaced than UHF antennas. In someexamples, this may facilitate use of antenna arrays within a device. Thepropagation of EHF transmissions, however, may be subject to evengreater atmospheric attenuation and shorter range than SHF or UHFtransmissions. The techniques disclosed herein may be employed acrosstransmissions that use one or more different frequency regions, anddesignated use of bands across these frequency regions may differ bycountry or regulating body.

The wireless communications system 100 may utilize both licensed andunlicensed radio frequency spectrum bands. For example, the wirelesscommunications system 100 may employ License Assisted Access (LAA),LTE-Unlicensed (LTE-U) radio access technology, or NR technology in anunlicensed band such as the 5 GHz industrial, scientific, and medical(ISM) band. When operating in unlicensed radio frequency spectrum bands,devices such as the base stations 105 and the UEs 115 may employ carriersensing for collision detection and avoidance. In some examples,operations in unlicensed bands may be based on a carrier aggregationconfiguration in conjunction with component carriers operating in alicensed band (e.g., LAA). Operations in unlicensed spectrum may includedownlink transmissions, uplink transmissions, P2P transmissions, or D2Dtransmissions, among other examples.

A base station 105 or a UE 115 may be equipped with multiple antennas,which may be used to employ techniques such as transmit diversity,receive diversity, multiple-input multiple-output (MIMO) communications,or beamforming. The antennas of a base station 105 or a UE 115 may belocated within one or more antenna arrays or antenna panels, which maysupport MIMO operations or transmit or receive beamforming. For example,one or more base station antennas or antenna arrays may be co-located atan antenna assembly, such as an antenna tower. In some examples,antennas or antenna arrays associated with a base station 105 may belocated in diverse geographic locations. A base station 105 may have anantenna array with a number of rows and columns of antenna ports thatthe base station 105 may use to support beamforming of communicationswith a UE 115. Likewise, a UE 115 may have one or more antenna arraysthat may support various MIMO or beamforming operations. Additionally,or alternatively, an antenna panel may support radio frequencybeamforming for a signal transmitted via an antenna port.

The base stations 105 or the UEs 115 may use MIMO communications toexploit multipath signal propagation and increase the spectralefficiency by transmitting or receiving multiple signals via differentspatial layers. Such techniques may be referred to as spatialmultiplexing. The multiple signals may, for example, be transmitted bythe transmitting device via different antennas or different combinationsof antennas. Likewise, the multiple signals may be received by thereceiving device via different antennas or different combinations ofantennas. Each of the multiple signals may be referred to as a separatespatial stream and may carry bits associated with the same data stream(e.g., the same codeword) or different data streams (e.g., differentcodewords). Different spatial layers may be associated with differentantenna ports used for channel measurement and reporting. MIMOtechniques include single-user MIMO (SU-MIMO), where multiple spatiallayers are transmitted to the same receiving device, and multiple-userMIMO (MU-MIMO), where multiple spatial layers are transmitted tomultiple devices.

Beamforming, which may also be referred to as spatial filtering,directional transmission, or directional reception, is a signalprocessing technique that may be used at a transmitting device or areceiving device (e.g., a base station 105, a UE 115) to shape or steeran antenna beam (e.g., a transmit beam, a receive beam) along a spatialpath between the transmitting device and the receiving device.Beamforming may be achieved by combining the signals communicated viaantenna elements of an antenna array such that some signals propagatingat particular orientations with respect to an antenna array experienceconstructive interference while others experience destructiveinterference. The adjustment of signals communicated via the antennaelements may include a transmitting device or a receiving deviceapplying amplitude offsets, phase offsets, or both to signals carriedvia the antenna elements associated with the device. The adjustmentsassociated with each of the antenna elements may be defined by abeamforming weight set associated with a particular orientation (e.g.,with respect to the antenna array of the transmitting device orreceiving device, or with respect to some other orientation).

A base station 105 or a UE 115 may use beam sweeping techniques as partof beam forming operations. For example, a base station 105 may usemultiple antennas or antenna arrays (e.g., antenna panels) to conductbeamforming operations for directional communications with a UE 115.Some signals (e.g., synchronization signals, reference signals, beamselection signals, or other control signals) may be transmitted by abase station 105 multiple times in different directions. For example,the base station 105 may transmit a signal according to differentbeamforming weight sets associated with different directions oftransmission. Transmissions in different beam directions may be used toidentify (e.g., by a transmitting device, such as a base station 105, orby a receiving device, such as a UE 115) a beam direction for latertransmission or reception by the base station 105.

Some signals, such as data signals associated with a particularreceiving device, may be transmitted by a base station 105 in a singlebeam direction (e.g., a direction associated with the receiving device,such as a UE 115). In some examples, the beam direction associated withtransmissions along a single beam direction may be determined based on asignal that was transmitted in one or more beam directions. For example,a UE 115 may receive one or more of the signals transmitted by the basestation 105 in different directions and may report to the base station105 an indication of the signal that the UE 115 received with a highestsignal quality or an otherwise acceptable signal quality.

In some examples, transmissions by a device (e.g., by a base station 105or a UE 115) may be performed using multiple beam directions, and thedevice may use a combination of digital precoding or radio frequencybeamforming to generate a combined beam for transmission (e.g., from abase station 105 to a UE 115). The UE 115 may report feedback thatindicates precoding weights for one or more beam directions, and thefeedback may correspond to a configured number of beams across a systembandwidth or one or more sub-bands. The base station 105 may transmit areference signal (e.g., a cell-specific reference signal (CRS), achannel state information reference signal (CSI-RS)), which may beprecoded or unprecoded. The UE 115 may provide feedback for beamselection, which may be a precoding matrix indicator (PMI) orcodebook-based feedback (e.g., a multi-panel type codebook, a linearcombination type codebook, a port selection type codebook). Althoughthese techniques are described with reference to signals transmitted inone or more directions by a base station 105, a UE 115 may employsimilar techniques for transmitting signals multiple times in differentdirections (e.g., for identifying a beam direction for subsequenttransmission or reception by the UE 115) or for transmitting a signal ina single direction (e.g., for transmitting data to a receiving device).

A receiving device (e.g., a UE 115) may try multiple receiveconfigurations (e.g., directional listening) when receiving varioussignals from the base station 105, such as synchronization signals,reference signals, beam selection signals, or other control signals. Forexample, a receiving device may try multiple receive directions byreceiving via different antenna subarrays, by processing receivedsignals according to different antenna subarrays, by receiving accordingto different receive beamforming weight sets (e.g., differentdirectional listening weight sets) applied to signals received atmultiple antenna elements of an antenna array, or by processing receivedsignals according to different receive beamforming weight sets appliedto signals received at multiple antenna elements of an antenna array,any of which may be referred to as “listening” according to differentreceive configurations or receive directions. In some examples, areceiving device may use a single receive configuration to receive alonga single beam direction (e.g., when receiving a data signal). The singlereceive configuration may be aligned in a beam direction determinedbased on listening according to different receive configurationdirections (e.g., a beam direction determined to have a highest signalstrength, highest signal-to-noise ratio (SNR), or otherwise acceptablesignal quality based on listening according to multiple beamdirections).

The wireless communications system 100 may be a packet-based networkthat operates according to a layered protocol stack. In the user plane,communications at the bearer or Packet Data Convergence Protocol (PDCP)layer may be IP-based. A Radio Link Control (RLC) layer may performpacket segmentation and reassembly to communicate over logical channels.A Medium Access Control (MAC) layer may perform priority handling andmultiplexing of logical channels into transport channels. The MAC layermay also use error detection techniques, error correction techniques, orboth to support retransmissions at the MAC layer to improve linkefficiency. In the control plane, the Radio Resource Control (RRC)protocol layer may provide establishment, configuration, and maintenanceof an RRC connection between a UE 115 and a base station 105 or a corenetwork 130 supporting radio bearers for user plane data. At thephysical layer, transport channels may be mapped to physical channels.

The UEs 115 and the base stations 105 may support retransmissions ofdata to increase the likelihood that data is received successfully.Hybrid automatic repeat request (HARQ) feedback is one technique forincreasing the likelihood that data is received correctly over acommunication link 125. HARQ may include a combination of errordetection (e.g., using a cyclic redundancy check (CRC)), forward errorcorrection (FEC), and retransmission (e.g., automatic repeat request(ARQ)). HARQ may improve throughput at the MAC layer in poor radioconditions (e.g., low signal-to-noise conditions). In some examples, adevice may support same-slot HARQ feedback, where the device may provideHARQ feedback in a specific slot for data received in a previous symbolin the slot. In other cases, the device may provide HARQ feedback in asubsequent slot, or according to some other time interval.

The wireless communications system 100 may be configured to supportdifferent traffic types (e.g., traffic categories, traffic priorities,service priorities), which may include or refer to communicationstraffic having different reliability thresholds, different latencythresholds, different services, or various combinations thereof. Forexample, the wireless communications system 100 may support a firsttraffic type (e.g., communications type), associated with relativelyhigh reliability targets or thresholds and relatively low latencytargets or thresholds, such as a URLLC traffic type. The wirelesscommunications system 100 may also support a second traffic type,associated with relatively low reliability targets or thresholds andrelatively long or relaxed latency thresholds, such an eMBB traffictype.

As an example, a PUSCH or a PUCCH transmission, including repetitions(if any), may be of priority index zero or of priority index one. Atransmission of priority index zero may be a low priority transmission,and a transmission of priority index one may be a high prioritytransmission. If a priority index is not provided to a UE 115 for aPUSCH or a PUCCH transmission, the priority index of the PUSCH or PUCCHtransmission may be zero.

In some cases, to support various system operations (e.g., efficientutilization of wireless communication resources, appropriate allocationor balancing of wireless communication resources, or appropriate supportof traffic according to different prioritizations or latencythresholds), the wireless communications system 100 may support dynamicresource sharing between traffic types, such as a dynamic allocation ofresources between URLLC communications and eMBB communications, or othercommunications, according to different traffic types, categories, orother prioritization s.

To support various uplink resource allocation techniques, a base station105 or other network entity (e.g., an entity of the core network 130 oran entity of a distributed base station 105) may allocate uplinkresources (e.g., an initial uplink resource allocation) to UEs 115, orgroups of UEs 115, for uplink transmissions. In some examples, a basestation 105 or other network entity may subsequently determine toperform a reallocation of the previously-allocated uplink resources,which may be triggered, for example, by a determined or detected need,demand, or request to support higher-priority communications. Thus, abase station 105 may transmit a new grant (e.g., to schedule anoverlapping transmission on at least a portion of thepreviously-allocated uplink resources or the base station 105 maytransmit an ULPI corresponding to at least a portion of thepreviously-allocated uplink resources. For example, a base station 105or other network entity may generate and transmit an ULPI (e.g., whichin some cases may be referred to as an uplink cancelation indication(ULCI)) that may correspond to at least a portion of thepreviously-allocated uplink resources (e.g., as allocated to particularUEs 115). UEs 115 may be configured to monitor for ULPIs, andaccordingly may determine, based at least in part on received, detected,or decoded ULPIs, whether or not to proceed with uplink transmissionsusing their previously-allocated uplink resources.

In some examples, a ULPI may be used to prevent a UE 115 from using atleast a portion of previously-allocated uplink resources for an uplinktransmission, which may support a dynamic allocation of uplink resourcesfrom communications associated with one latency threshold tocommunications associated with another latency threshold, or some otherreallocation based on communications prioritization. For example,resources that were originally allocated to a UE 115 for eMBBcommunications (e.g., allocated to eMBB UEs, such as UEs 115 configuredfor eMBB communications) may be reallocated to the same UE 115, or adifferent UE 115, for URLLC communications (e.g., a reallocation towardsmore performance-sensitive communications). For example, wirelesscommunications system 100 may support intra-UE dynamic uplink resourceallocation (e.g., where a base station 105 may reallocate resourcesoriginally allocated to the UE 115 to the same UE) and inter-UE dynamicuplink resource allocation (e.g., where a base station 105 mayreallocate resources originally allocated to one UE 115 to a differentUE 115). Thus, according to these and other examples, various types ofuplink resource allocations may be canceled, preempted, or reallocated,such that the wireless communications system 100 may support a moredynamic redistribution of uplink resources according to differentpriorities of communications.

As discussed herein, wireless communications system 100 may employ oneor more scheduling constraints that may be defined regarding uplinktransmissions (e.g., such as overlapping PUSCH and PUCCH transmissions,overlapping PUSCH transmissions, etc.). For example, wirelesscommunications system 100 may support one or more scheduling constraintsto support efficient utilization of intra-UE and inter-UE handling ofoverlapping scheduled transmissions. For instance, wirelesscommunications system 100 may implement scheduling constraints that maydefine how a UE 115 may apply intra-UE and inter-UE multiplexing andcancelation rules in various scenarios. For example, a UE 115 may applyintra-UE cancelation rules (e.g., potentially resulting in a droppeduplink transmission) before inter-UE cancelation rules. In someexamples, later-received grants or later-received ULPIs (e.g., from abase station 105) may not change the UE 115′s decision to drop theuplink transmission. As another example of a scheduling constraint, a UE115 may not expect to receive a grant, from a base station 105, for anuplink transmission that would arise in subsequent cancelation of thatuplink transmission due to a grant or ULPI previously received from thebase station 105.

FIG. 2 illustrates an example of a wireless communications system 200that supports techniques for intra-UE and inter-UE cancelation ofoverlapping communications in accordance with aspects of the presentdisclosure. In some examples, wireless communications system 200 mayimplement aspects of wireless communications system 100. The wirelesscommunications system 200 may include a base station 105-a that supportscommunication with multiple UEs (e.g., UE 115-a and UE 115-b) within asupported geographic coverage area 110-a. The base station 105-a maycommunicate with the UE 115-a on resources of a carrier 205-a, and thebase station 105-a may communicate with the UE 115-b on resources of acarrier 205-b. In some examples, the communication may support missioncritical applications that include stringent communication performance(e.g., reliability thresholds, latency thresholds) along withcommunications of other types. Wireless communications system 200 mayimplement aspects of wireless communications system 100, as describedwith reference to FIG. 1 .

Generally, wireless communication system 200 illustrates an examplewhere base station 105-a may act as a serving or source base station forUE 115-a and UE 115-b. For example, base station 105-a may scheduleuplink and/or downlink communications between base station 105-a and UEs115-a and 115-b. The scheduled communications may utilize dynamicallyand/or semi-statically configured resources, e.g., such as time,frequency, spatial, and/or code resources. In some aspects, base station105-a may autonomously schedule such communications and/or allocateappropriate resources, or may do so in conjunction with one or morenetwork entities, such as a core network. The downlink communicationsmay include transmissions from base station 105-a to UE 115-a and/or UE115-b and the uplink communications may include transmissions from UE115-a and/or UE 115-b to base station 105-a.

Communications between base station 105-a and UEs 115 may include dataand/or control information being communicated. For example, a datatransmission may be communicated over a corresponding data channel, suchas a physical downlink shared channel (PDSCH) and/or PUSCH. A controltransmission may be communicated over a corresponding control channel,such as a physical downlink control channel (PDCCH) and/or PUCCH.Examples of control information being communicated may include, but arenot limited to, acknowledgment/negative-acknowledgment (ACK/NACK)feedback, channel state information (CSI), scheduling request (SR), andthe like. In the downlink, such control information may be referred toas downlink control information (DCI). In the uplink, such controlinformation may be referred to more generally as uplink controlinformation (UCI).

In some wireless communication systems, UEs 115 may be configured orotherwise scheduled to transmit uplink control information (e.g.,ACK/NACK, CSI, SR, etc., communicated in an uplink control transmission)that collides (e.g., overlaps) in the time domain with an uplink datatransmission (e.g., a PUSCH transmission). In this situation, UEs 115may be allowed to piggyback (e.g., multiplex) the uplink controlinformation (e.g., ACK/NACK) into the uplink data transmission (e.g.,PUSCH).

In the wireless communications system 200, UE 115-a and UE 115-b maysupport different service deployments, such as URLLC services and eMBBservices. For example, the UE 115-a may support URLLC transmissions toreduce end-to-end latency for data transmissions and receptionsassociated with the base station 105-a. In some examples, the UE 115-amay correspond to a URLLC UE that supports or is otherwise configuredfor transmissions, such as periodic transmissions, of relatively smalldata packets. For example, the UE 115-a may include a URLLC UE thatsupports operations and data communication associated with factoryautomation (e.g., automated manufacturing, supply chain management),transport (e.g., vehicle-to-vehicle (V2V) communications,vehicle-to-infrastructure (V2I) communications), or electrical powerdistribution (e.g., power grid networking) within a supported area orlocale, among other possible implementations.

Additionally, or alternatively, the UE 115-b may support eMBBtransmissions associated with high data rates across wide coverage areas(such as geographic coverage area 110-a) supported by the base station105-a. In some examples, compared to URLLC communications, eMBBcommunications may be associated with relatively relaxed (e.g., longer)latency targets or thresholds, lower reliability targets or thresholds,or both. Moreover, one or more of UE 115-a and UE 115-b may support datacommunications associated with multiple service deployments (such asURLLC and eMBB), as part of an intra-UE or inter-UE operation.

To support the conditions associated with the URLLC and eMBB servicedeployments, or other types of resource allocation based oncommunication prioritization, the base station 105-a and the UEs 115-aand 115-b may support various techniques for dynamic uplink resourceallocations and uplink transmission cancelation or preemption. Forexample (e.g., for inter-UE dynamic resource allocation techniques), thebase station 105-a may be configured to transmit a ULPI based at leastin part on determining a reallocation of uplink resources (e.g.,associated with uplink resources allocated to one or both of the UE115-a or 115-b), and the UEs 115-a and 115-b may monitor for such ULPIsto determine how they should proceed with uplink communications. Inother words, the UEs 115 may be notified about canceled uplink resourcesin the time domain and frequency domain. In various examples, each ofthe UE 115-a or the UE 115-b may perform uplink communicationdeterminations such as determining whether to perform or proceed withuplink transmissions using at least a portion of theirpreviously-allocated uplink resources, or determining to refrain fromusing at least a portion of their previously-allocated uplink resources,or determining to await another allocation of uplink resources beforeinitiating or resuming uplink communications, or other determinations.

ULPIs may be signaled by the base station 105-a to UEs 115 (e.g., one orboth of the UEs 115-a or 115-b or a group of UEs) according to varioustechniques. For example, a UE 115 may be configured to monitor for ULPIsaccording to various signaling by the base station 105-a, such asvarious types of downlink control signaling, physical channel signaling,cell-specific signaling, and others. In some examples, ULPIs may beconveyed in DCI over a PDCCH, which may support UE-specific ULPIs. Insome examples, a UE 115 may be configured (e.g., by the base station 105a) with a radio network temporary identifier (RNTI) for monitoring aPDCCH that may be carrying ULPIs. In various examples, a UE 115 may beconfigured with an RNTI that is common between uplink and downlinkcancelation or preemption indications, or different between uplink anddownlink cancelation or preemption indications. In some examples, ULPIsmay be configured or conveyed in a group-common physical downlinkcontrol channel (GC-PDCCH) or otherwise conveyed in group-common DCI(GC-DCI), or DCI format 2_1, which may support signaling ULPIs that arerelevant to sets of one or more UEs 115, and may reduce signalingoverhead as compared to ULPIs that are conveyed in UE-specificsignaling. In some examples, ULPIs, or GC-PDCCH or GC-DCI indications,may be configured for UEs 115 configured for particular communications,such as eMBB communications (e.g., configured for eMBB UEs).

Further (e.g., for intra-UE dynamic resource allocation techniques), thebase station 105-a may be configured to transmit a grant (e.g., a newgrant, a subsequent grant, etc.) based at least in part on determining areallocation of uplink resources (e.g., associated with uplink resourcespreviously allocated to a particular UE). UEs 115-a and 115-b maymonitor for grants to determine how they should proceed with uplinkcommunications. In other words, a UE 115 may receive a grant schedulingan uplink transmission over some resources. In some cases, the UE 115may receive another grant (e.g., later in time) and be notified that thepreviously scheduled resources in the time domain and frequency domainoverlap with the newly scheduled uplink transmission. In variousexamples, each of the UE 115-a or the UE 115-b may perform uplinkcommunication determinations such as determining whether to perform orproceed with uplink transmissions using at least a portion of theirpreviously-allocated uplink resources, or determining to refrain fromusing at least a portion of their previously-allocated uplink resources,or determining to await another allocation of uplink resources beforeinitiating or resuming uplink communications, or other determinations.

In the example of FIG. 2 , base station 105-a may transmit grants 210(e.g., uplink grants 210, downlink grants 210) and ULPIs 215 to UE 115-aand UE 115-b for dynamic resource allocation techniques describedherein. As discussed herein, wireless communications system 200 maysupport services with different reliability/latency requirements (e.g.,such as eMBB communications, URLLC, communications, etc.). As such,wireless communications system 200 may dynamically multiplex UEs 115with different services in the same time-frequency resource to achievebetter spectrum utilization (e.g., according to intra-UE multiplexingand cancelation, as well as inter-UE multiplexing and cancelation).

Wireless communications system 200 may support intra-UE multiplexing andcancelation (e.g., dropping) for uplink when two uplink channels (e.g.,two scheduled uplink transmissions) collide (e.g., overlap). If twouplink channels of the same priority collide, then the UE 115 maymultiplex the payload in one uplink transmission. For example, if PUCCHcollides with another PUCCH, a UE 115 may multiplex the UCI payload ofthe two channels and transmit them in one PUCCH. As another example, ifPUSCH collides with another PUCCH, a UE 115 may piggyback the UCI of thePUCCH on the PUSCH transmission and transmit the PUSCH. Alternatively,if two uplink channels of different priorities collide, the UE may dropthe channel with the lower priority. For example, for a high priorityPUSCH colliding with a low priority PUSCH, the low priority PUSCH isdropped or canceled, and the high priority PUSCH is transmitted.

Further, wireless communications system 200 may support inter-UEmultiplexing and cancelation (e.g., dropping) for uplink when two uplinkchannels collide (e.g., overlap). In other words, in addition tointra-UE multiplexing and cancelation, wireless communications system200 may support preemption indications (PIs) (e.g., ULPIs and DLPIs) forinter-UE multiplexing and cancelation. PIs may allow base station 105-ato schedule URLLC transmissions on resources that were allocated to eMBBUEs 115 (e.g., base station 105-a may schedule URLLC transmissions forUE 115-a on resources previously allocated for eMBB transmission for UE115-b). In the uplink, base station 105-a may use ULPI to indicate tothe eMBB UEs to cancel part of its transmission (e.g., any or all of atransmission that overlaps with the URLLC transmission from otherusers). ULPI may be transmitted before the affected eMBB PUSCHtransmission. In such scenarios, the eMBB UE may cancel the overlappingpart of its transmission after receiving the ULPI, hence not interferingwith the URLLC.

For PIs, time and frequency resources may be divided into a X*Y grid,where X represents the frequency domain and Y represents the timedomain. The PI may indicate whether a corresponding frequency-time part(e.g., a frequency-time part on the X*Y grid) is preempted or not. Forexample, each location on the X*Y grid may correspond to afrequency-time part, and a ULPI may include a bit sequence thatcorresponds to each location on the X*Y grid (e.g., and thus a bit thatcorresponds to each frequency-time part). If the bit is set to ‘1’ theULPI may indicate that the corresponding frequency-time part ispreempted (e.g., if the bit is set to ‘0’ the ULPI may indicate that thecorresponding frequency-time part is available).

A UE 115 may thus receive an ULPI and may compare any uplinktransmissions (e.g., any scheduled uplink transmissions) with the ULPI.The UE 115 may thus preempt any uplink transmissions starting from thefirst overlapping OFDM symbol indicated by the ULPI. In some cases, ifthere are remaining transmission resources for the UE after preemption,the UE 115 may also cancel the remaining transmission resources (e.g.,an ULPI may cause a UE 115 to cancel or drop a transmission, withoutresume, if the ULPI indicates frequency-time parts that at leastpartially overlap with the uplink transmission). In some examples, ULPImay only cancel PUSCH and sounding reference signal (SRS) transmissions(e.g., but ULPI may not cancel PUCCH). Further, a UE 115 may or may notadhere to ULPI (e.g., a UE 115 may or may not preempt resourcesindicated by an ULPI) when the ULPI preempts a high prioritytransmission (e.g., a high priority PUSCH).

However, in some scenarios, such techniques for dynamic resourceallocation may be ambiguous or otherwise deficient. As an example, a UE115 may receive a first grant 210 (e.g., for a low priority PUSCH)followed by a second grant 210 (e.g., for a high priority PUCCH) and, inaccordance with the rules mentioned above, the UE 115 may decide to dropone of the scheduled transmissions (e.g., the low priority PUSCHscheduled by the first grant 210). However, it is also possible that theUE 115 may receive a third grant 210 (e.g., for a high priority PUSCH)which might allow for the previously scheduled high priority PUCCH to bemultiplexed with the newly scheduled high priority PUSCH. In so doing,the third grant may remove the condition which caused the UE 115 toelect to drop the low priority PUSCH. For instance, when the highpriority PUCCH is piggybacked on the high priority PUSCH, the highpriority PUCCH (e.g., which initially caused the UE 115 to determine todrop the low priority PUSCH) may no longer overlap with the low priorityPUSCH (e.g., as the UCI of the high priority PUCCH may be piggybackedonto the high priority PUSCH, and the high priority PUSCH may beassociated with different resources than the resources of the highpriority PUCCH that overlapped with the dropped low priority PUSCH).

As such, according to the techniques described herein, wirelesscommunications system 200 may implement one or more schedulingconstraints to support efficient utilization of dynamic resourceallocation (e.g., to support efficient intra-UE and inter-UE handling ofoverlapping scheduled transmissions which may allow a UE 115 to resolveoverlapping between transmissions). For example, the describedscheduling constraints may define how a UE 115 may apply intra-UE andinter-UE multiplexing and cancelation rules for various scenarios. Forinstance, a UE 115 may apply intra-UE cancelation rules (e.g.,potentially resulting in a dropped uplink transmission) before inter-UEcancelation rules. In some examples, later-received grants 210 orlater-received ULPIs 215 may not change a UE's decision to drop anuplink transmission. As another example of a scheduling constraint, a UEmay not expect to receive a grant 210 for an uplink transmission thatwould arise in subsequent cancelation of that uplink transmission due toa previously-received grant 210 or a previously-received ULPI 215.

Thus, according to these and other examples, various uplink resourceallocations may be unambiguously canceled, preempted, or reallocated,thereby supporting efficient dynamic allocation, preemption, andredistribution of uplink resources in wireless communication system 200.Wireless communications system 200 may more-effectively balance theperformance and resource utilization of communications according todifferent priorities. Such may provide for more efficient resourceutilization and resource reallocation within wireless communicationssystem 200 supporting various different service deployments. Further,the described techniques (e.g., the described scheduling constraints)may provide for reduced computational complexity at UEs 115 (e.g., dueto the alleviated handling of ambiguous scenarios where a UE 115 mayotherwise transition back and forth between determinations of whether tocancel or perform an uplink transmission).

FIG. 3A illustrates an example of a scheduling diagram 300 that supportstechniques for intra-UE and inter-UE cancelation of overlappingcommunications in accordance with aspects of the present disclosure. Insome examples, scheduling diagram 300 may implement aspects of wirelesscommunications system 100 and/or wireless communications system 200.Scheduling diagram 300 may illustrate an example of intra-UE resourcecancelation for dynamic resource allocation techniques described herein.

For example, a UE may receive low priority (LP) DCI 305 (e.g., an uplinkgrant including DCI scheduling a low priority uplink transmission) whichmay schedule LP PUSCH 315 (e.g., a low priority uplink datatransmission). After the LP DCI 305 (e.g., and prior to the LP PUSCH315), a UE may receive high priority (HP) DCI 310 (e.g., a downlinkgrant for a high priority downlink transmission along with an associatedhigh priority uplink control channel transmission) and may schedule HPPUCCH 320 that overlaps at least partially in time (e.g., collides) withthe previously scheduled LP PUSCH 315 (e.g., from, in the presentexample, t₁ to t₂).

Generally, to resolve collisions (or overlapping) between uplinktransmissions, a UE may first resolve collisions between uplinktransmissions with same priority and then resolve collisions betweenuplink transmissions with different priorities. Resolving collisions assuch, a UE may be left with a single uplink transmission. For instance,by resolving all collisions with the same priority first, a UE may beleft with at most two channels (e.g., after resolving all collisions ofhigh priority leaving one high priority channel and resolving allcollisions of low priority leaving one low priority channel). Next, theUE may resolve collisions between uplink transmissions with differentpriorities such that, for example, if two channels remain after thefirst step, the UE may then resolve the remaining two channels andselect the channel with higher priority for transmission.

Further, when a high priority uplink transmission (e.g., HP PUCCH 320)overlaps with a low priority uplink transmission (e.g., LP PUSCH 315) ina slot, the UE may cancel the low priority uplink transmission startingfrom a deterministic time (T_(proc,2)+d₁) after the end of PDCCHscheduling the high priority transmission (e.g., after the end of the HPDCI 310). For example, T_(proc,2) may correspond to a UE processing timecapability of a carrier and d₁ may be the time duration corresponding tothe number (e.g., 0, 1, 2) of symbols reported by UE capability (e.g.,note: d_(1,2)=0 may be for cancelation). The processing time (e.g., theminimum processing time) of the high priority channel (e.g., of HP PUCCH320) may be extended by d2 symbols (e.g., where d2 may be the timeduration corresponding to a number (e.g., 0, 1, 2) of symbols reportedby UE capability). Generally, the overlapping condition may be perrepetition of the uplink transmission.

In the example scheduling diagram 300, a UE may partially drop the lowpriority channel (e.g., the UE may partially drop LP PUSCH 315 afterT_(proc,2)+d₁ from the end of HP DCI 310 scheduling the HP PUCCH 320).The UE may then transmit the HP PUCCH 320 based on the dropping of theoverlapping LP PUSCH 315. However, as discussed herein, in some casessuch techniques for dynamic resource allocation may be ambiguous orotherwise deficient without the scheduling constraints described herein(e.g., as described in more detail here, for example, with reference toexample scheduling diagrams 301, 400, 500, and 501).

FIG. 3B illustrates an example of a scheduling diagram 301 that supportstechniques for intra-UE and inter-UE cancelation of overlappingcommunications in accordance with aspects of the present disclosure. Insome examples, scheduling diagram 301 may implement aspects of wirelesscommunications system 100 and/or wireless communications system 200.Scheduling diagram 301 may illustrate an example of a cancelationdetermination permanency scheduling constraint in accordance withaspects of the techniques described herein. For example, in somescenarios, a cancelation determination permanency scheduling constraintmay avoid intra-UE multiplexing and cancelation ambiguity, reducecomputational complexity at the UE, etc., and may generally provide formore efficient dynamic resource allocation within wirelesscommunications systems.

For example, a UE may receive LP DCI 305 (e.g., an uplink grantincluding DCI scheduling a low priority uplink transmission) which mayschedule LP PUSCH 315 (e.g., a low priority uplink data transmission).After the LP DCI 305 (e.g., and prior to the LP PUSCH 315), a UE mayreceive HP DCI 310 (e.g., a downlink grant for a high priority downlinktransmission along with an associated high priority uplink controlchannel transmission) and may schedule HP PUCCH 320 that overlaps atleast partially in time (e.g., collides) with the previously scheduledLP PUSCH 315. As such, the UE may initially determine to drop the LPPUSCH 315 and transmit the HP PUCCH 320 (e.g., as described withreference to example scheduling diagram 300). That is, the UE mayoperate in accordance with a scheduling constraint that may indicatethat the UE is to prioritize the HP PUCCH 320 over the LP PUSCH 315(e.g., transmit the high priority uplink transmission and cancel the lowpriority uplink transmission).

However, in some cases, the UE may then receive an additional grant(e.g., HP DCI 325) scheduling an additional uplink transmission (e.g.,scheduling HP PUSCH 330) prior to when the UE drops the LP PUSCH 315(e.g., but after the UE has already made the decision to drop the LPPUSCH 315 at a time T_(proc,2)+d₁ after the received HP DCI 310). Insuch scenarios and in similar scenarios, without the one or morescheduling constraints described herein, the UE may need to first handlethe two overlapping transmissions with the same priority (e.g., HP PUCCH320 and HP PUSCH 330) according to intra-UE multiplexing and cancelationtechniques described herein (e.g., according to intra-UE multiplexingand cancelation techniques without the described cancelationdetermination permanency scheduling constraint). That is, when resolvingHP PUCCH 320 and HP PUSCH 330, the UE may determine to piggyback UCI ofthe HP PUCCH 320 on the HP PUSCH 330 and transmit the HP PUSCH 330. Inother words, the UE may operate in accordance with a schedulingconstraint that may indicate that the UE is to piggypack UCI of the HPPUCCH 320 on the HP PUSCH 330 (e.g., transmit the high priority uplinkdata transmission and cancel the high priority uplink controltransmission). As such, HP PUCCH 320 may no longer overlap or collidewith LP PUSCH 315. However, as discussed, the UE may have previouslydetermined to cancel or drop the LP PUSCH 315 based on the two grants(e.g., LP DCI 305 and HP DCI 310) received prior to the additional grant(e.g., HP DCI 325).

Once a UE makes such a cancelation decision (e.g., for LP PUSCH 315), itmay be computationally complex, time consuming, etc. to revert such adecision. In other words, it may be burdensome (e.g., in terms ofcomputational capability, power consumption, etc.) on the UE to undo acancelation determination and instead revert back to transmitting theuplink transmission (e.g., the LP PUSCH 315). However, according toconventional techniques for intra-UE multiplexing and cancelation fordynamic resource allocation (e.g., according to techniques without thedescribed scheduling constraints), a base station may still expect toreceive LP PUSCH 315 (e.g., as, in accordance with the UE handling samepriority transmissions before different priority transmissions for alloverlapped transmissions, LP PUSCH 315 does not overlap with HP PUSCH330 that includes HP PUCCH 320 piggybacking and HP PUCCH 320cancelation). As such, the UE may problematically revert itsdetermination to cancel LP PUSCH 315 and proceed to transmit the LPPUSCH 315 (e.g., which may be inefficient or, in some cases, notpossible), or the UE may not transmit LP PUSCH 315 even though a basestation may expect the transmission (e.g., which may result ininefficient use of system resources).

The one or more scheduling constraints described herein may generallyimprove dynamic resource allocation. For example, wirelesscommunications systems may implement a cancelation determinationpermanency scheduling constraint, such that once a cancelationdetermination is made the determination to cancel the transmission ismaintained. In one aspect, once a UE resolves overlapping between uplinktransmissions with different priorities in accordance with a firstscheduling constraint, the UE may resolve overlapping between uplinktransmissions with the same priority in accordance with a secondscheduling constraint. Thus, the second scheduling constraint may referto a scheduling constraint used to resolve overlapping between uplinktransmissions with the same priority, or the second schedulingconstraint may refer to the cancelation determination permanencyscheduling constraint which may indicate that a UE is to maintain adecision to cancel a transmission once the decision is made. Forinstance, when a UE receives a second grant (e.g., HP DCI 310), the UEdoes not know that there will be an additional grant (e.g., HP DCI 325)in the future. Therefore, to avoid problematic scenarios (e.g., asdiscussed above) that may result in burdensome computational complexityat the UE, inefficient resource utilization (e.g., if the UE cannottransmit the LP PUSCH 315 that a base station is expecting), etc., thescheduling constraint (e.g., the cancelation determination permanencyscheduling constraint) may be implemented as described herein.

A scheduling constraint (e.g., a cancelation determination permanencyscheduling constraint) may be set by wireless communications systems toconfigure UEs to not look ahead or not make decisions based on futuretransmissions (e.g., based on future grants, such as based on possibleHP DCI 325 at the time of reception of HP DCI 310). That is, when a UEdetermines to cancel a low priority transmission (e.g., LP PUSCH 315)due to conflict with a high priority transmission (e.g., HP PUCCH 320)scheduled by a PDCCH (e.g., HP DCI 310), the UE may not consider anyother PDCCHs that is received after the end of the first PDCCH (e.g.,the UE may determine to cancel LP PUSCH 315 after receiving HP DCI 310,without later considering HP DCI 325). In other words, once a decisionto cancel a transmission (e.g., LP PUSCH 315) is made, the UE may notchange its mind and un-cancel the transmission (e.g., LP PUSCH 315).Thus, the scheduling constraint may provide that the UE is allowed toresolve conflicts (or overlapping) between uplink transmissionsassociated with different priorities before (or after) resolvingconflicts between uplink transmissions associated with the samepriority. Note that, in this case, the second PDCCH (e.g., HP DCI 325)may be either a PDCCH scheduling another high priority transmission or agroup-common PDCCH (e.g., an ULPI, or slot format indicator (SFI)).

For example, if a UE determines to transmit a first PUCCH of largerpriority index in response to a first PDCCH (e.g., and the first PUCCHoverlaps with a second PUCCH or a PUSCH of smaller priority index)and/or a PUSCH of larger priority index scheduled by a second PDCCHafter the first PDCCH (e.g., and the UE would multiplex the UCI of thefirst PUCCH on the PUSCH of larger priority index), then the UE maycancel the second PUCCH or the PUSCH of smaller priority index startingfrom at least T_(proc,2) d₁ symbols after the end of the last symbol ofthe first PDCCH.

Such a scheduling constraint may avoid potentially ambiguous situationsby UEs not looking ahead, or by UEs resolving overlapping transmissionsbased on presently known information without considering potentialchanges that may arise from additional grants that have not beenreceived (e.g., that may or may not be transmitted to the UE). As such,wireless communications systems may more efficiently utilize resources(e.g., and may more efficiently conduct dynamic resource allocationtechniques) when implementing scheduling constraints (e.g., such as thedescribed cancelation determination permanency scheduling constraint).For instance, upon initial transmission of LP DCI 305 and subsequenttransmission of HP DCI 310, a base station may become aware that the UEwill drop LP PUSCH 315. In scenarios where the base station stilltransmits HP DCI 325 at a later time, the base station may acknowledgethe cancelation determination permanency scheduling constraint and mayidentify that the cancelation of LP PUSCH 315 will be maintained by theUE (e.g., such that the base station may know not to expect LP PUSCH315, and such that the base station may reallocate or otherwise reuseresources associated with dropped LP PUSCH 315, which may improvespectral efficiency, reduce latency, etc.).

It should be noted that the grants described above (one grant includingHP DCI 310 and a second grant including HP DCI 325) may be assumed to bein different PDCCHs (e.g., such that after receipt of a PDCCH includingHP DCI 310, the UE determines to cancel LP PUSCH 315 prior to anyreceipt of a subsequent PDCCH including the HP DCI 325). In a scenariowhere the HP DCI 310 and HP DCI 325 are received in a single PDCCH, suchambiguity of future HP PUSCH 330 scheduling may not arise as the HP DCI310 and HP DCI 325 are received in a single PDCCH (e.g., at the sametime). In such a scenario, the UE may resolve HP PUCCH 320 and HP PUSCH330 first and proceed to transmit both LP PUSCH 315 and HP PUSCH 330(e.g., with HP PUCCH 320 piggybacking on HP PUSCH 330). As such,generally as used herein, an additional grant may refer to a grantreceived in a PDCCH monitoring occasion later in time than the PDCCHmonitoring occasion that includes a grant resulting in a multiplexing orcancelation determination.

Further, it should be noted that the described scheduling constraint(e.g., the described cancelation determination permanency schedulingconstraint) does not result in total ignorance of any additional grantsreceived after a cancelation decision has been made in accordance withthe cancelation determination permanency scheduling constraint. As usedherein, a UE may “discard” an additional grant in regards to thecancelation decision, however the additional grant may still be observedfor other future transmissions. For instance, in the example schedulingdiagram 301, the UE may discard the HP DCI 325 in terms of anyscheduling decisions pertaining to the already determined cancelation ofLP PUSCH 315. However, the UE may still decode the HP DCI 325 (e.g., theadditional grant) and deal with any overlapping transmissionsaccordingly.

That is, after a UE initially received LP DCI 305 and then subsequentlyreceives HP DCI 310, the UE may determine to cancel LP PUSCH 315. Uponreceipt of an additional grant (e.g., HP DCI 325), the UE may discard(e.g., ignore, not consider, etc.) the ramifications or impacts of theadditional grant on the already established scheduling decisions (e.g.,on the decision to drop LP PUSCH 315). However, the UE may still processthe additional grant (e.g., HP DCI 325) and may proceed according todynamic resource allocation techniques described herein (e.g., afterdropping LP PUSCH 315, the UE may identify overlap between HP PUCCH 320and HP PUSCH 330, multiplex UCI of HP PUCCH 320 on to HP PUSCH 330, andtransmit the HP PUSCH 330 with the piggybacking). In other words, upon adecision or determination to cancel a transmission (e.g., a low prioritytransmission), the UE may not take into account (e.g., the UE maydiscard as far as any present scheduling decisions are concerned) anyadditional grants (e.g., in subsequent PDCCH) that may or may not bereceived prior to the dropping of the low priority transmission.However, the UE still honors the additional grant to resolve subsequentcollisions (e.g., between the first uplink transmission, such as HPPUCCH 320, and additional uplink transmissions, such as HP PUSCH 330).

In some implementations of the described cancelation determinationpermanency scheduling constraint, wireless communications systems (e.g.,UEs and base stations) may define such scheduling constraints as errorcases. For example, a UE may not expect to be scheduled by a first PDCCH(e.g., a PDCCH including HP DCI 310) to cancel an uplink transmission(e.g., LP PUSCH 315), and then to receive a second PDCCH (e.g., a PDCCHincluding HP DCI 325) after the first PDCCH, where the second PDCCHchanges the cancelation behavior. In other words, in some cases,wireless communications systems may implement the cancelationdetermination permanency scheduling constraint in the form of notallowing such scenarios to be configured (e.g., in the form oftriggering an error case when a PDCCH changes the cancelation behaviorcaused by a previous PDCCH conveyed earlier in time).

FIG. 4 illustrates an example of a scheduling diagram 400 that supportstechniques for intra-UE and inter-UE cancelation of overlappingcommunications in accordance with aspects of the present disclosure. Insome examples, scheduling diagram 400 may implement aspects of wirelesscommunications system 100, wireless communications system 200,scheduling diagram 300, and/or scheduling diagram 301. Schedulingdiagram 400 may illustrate an example of an intra-UE/inter-UE orderingscheduling constraint in accordance with aspects of the techniquesdescribed herein. For example, in some scenarios, an intra-UE/inter-UEordering scheduling constraint may avoid multiplexing and cancelationambiguity, reduce computational complexity at the UE, etc., and maygenerally provide for more efficient dynamic resource allocation withinwireless communications systems.

For example, a UE may receive a first grant (e.g., a grant including LPDCI 405) that may schedule a first uplink transmission (e.g., LP PUCCH415). After the LP DCI 405, the UE may receive a second grant (e.g., HPDCI 410) that may schedule a second uplink transmission (e.g., HP PUSCH420). Therefore, HP DCI 410 may schedule HP PUSCH 420 that overlaps atleast partially in time (e.g., collides) with the previously scheduledLP PUCCH 415 (e.g., from, in the present example, t₁ to t₂). As such,the UE may initially determine to drop the LP PUCCH 415 and transmit theHP PUSCH 420.

However, in some cases, the UE may then receive an additional indication(e.g., ULPI 425) which may indicate a frequency-time part that at leastpartially overlaps with HP PUSCH 420 (e.g., but after the UE has alreadymade the decision to drop the LP PUCCH 415 at a time T_(proc,2)+d₁ afterthe received HP DCI 410). In such scenarios and in similar scenarios,without the one or more scheduling constraints described herein, the UEmay determine to drop the low priority uplink transmission and maylater, upon receipt of the ULPI 425, identify the overlap with the lowpriority uplink transmission no longer exists and try to un-cancel thedropped low priority uplink transmission.

That is, ULPI 425 may preempt a frequency-time part that at leastpartially overlaps with HP PUSCH 420 such that a UE may cancel HP PUSCH420. As such, the overlap or collision between HP PUSCH 420 and LP PUCCH415 may no longer be present. As discussed herein, once a UE makes sucha cancelation decision (e.g., for LP PUCCH 415), it may becomputationally complex, time consuming, etc. to revert such a decision.In other words, it may be burdensome (e.g., in terms of computationalcapability, power consumption, etc.) on the UE to undo a cancelationdetermination and instead revert back to transmitting the uplinktransmission (e.g., the LP PUCCH 415). However, according toconventional techniques for dynamic resource allocation (e.g., accordingto techniques without the described scheduling constraints), a basestation may still expect to receive LP PUCCH 415 (e.g., as after ULPI425, the LP PUCCH 415 does not overlap with canceled HP PUSCH 420). Assuch, the UE may problematically revert its determination to cancel LPPUCCH 415 and proceed to transmit the LP PUCCH 415 (e.g., which may beinefficient or, in some cases, not possible), or the UE may not transmitLP PUCCH 415 even though a base station may expect the transmission(e.g., which may result in inefficient use of system resources).

The one or more scheduling constraints described herein may generallyimprove dynamic resource allocation. For example, wirelesscommunications systems may implement an intra-UE/inter-UE orderingscheduling constraint, such that a UE always applies PIs after intra-UEmultiplexing and dropping/cancelation has been performed. The UE mayperform dropping/cancelation in accordance with a PI (e.g., afterreceiving DCI with DCI format 2_4) on uplink transmissions determinedfrom performing intra-UE multiplexing and dropping/cancelation. Forinstance, when a UE resolves overlapping transmissions, the UE may firstresolve intra-UE collisions and then resolve inter-UE collisions (e.g.,resolve any received PIs). In other words, the decision to resolveintra-UE overlapping uplink channels may not be impacted by the ULPI.Therefore, to avoid problematic scenarios (e.g., as discussed above)that may result in burdensome computational complexity at the UE,inefficient resource utilization (e.g., if the UE cannot transmit the LPPUCCH 415 that a base station is expecting), etc., the schedulingconstraint (e.g., the intra-UE/inter-UE ordering scheduling constraint)may be implemented as described herein.

For instance, if a UE would transmit multiple overlapping PUCCHs andPUSCHs or SRSs or multiple overlapping PUSCHs and SRSs, and if the UEdetects a DCI (e.g., a DCI format 2_4, an ULPI, etc.) to cancel at leastone of the PUSCH transmissions or SRS transmissions, the UE behavior toresolve the overlapping among the multiple overlapping PUCCHs, PUSCHsand SRSs may not change due to detection of DCI (e.g., DCI format 2_4).

Such a scheduling constraint may avoid potentially ambiguous situationswhere a UE and/or base station may be unaware of whether or not a UEwill be able to transmit an uplink transmission previously canceled(e.g., due to timing of grants and/or PIs, such as due to the timing ofULPI 425 after HP DCI 410 in the example of FIG. 4 ). As such, wirelesscommunications systems may more efficiently utilize resources (e.g., andmay more efficiently conduct dynamic resource allocation techniques)when implementing scheduling constraints (e.g., such as the describedintra-UE/inter-UE ordering scheduling constraint). For instance, uponinitial transmission of LP DCI 405 and subsequent transmission of HP DCI410, a base station may become aware that the UE will drop LP PUCCH 415in accordance with the handling of intra-UE multiplexing/cancelationprior to any inter-UE multiplexing/cancelation. In other words, a basestation may be aware that the UE will drop LP PUCCH 415 after receipt ofHP DCI 410 regardless of any subsequent PIs transmitted by the basestation (e.g., as the UE will handle intra-UE multiplexing/cancelationfirst in accordance with the intra-UE/inter-UE ordering schedulingconstraint).

In scenarios where the base station transmits additional or subsequentPIs at a later time (e.g., such as ULPI 425 after HP DCI 410 and LP DCI405), the base station may acknowledge the intra-UE/inter-UE orderingscheduling constraint and may identify that the cancelation of LP PUCCH415 will be performed by the UE regardless based on intra-UEmultiplexing/cancelation (e.g., such that the base station may know notto expect LP PUCCH 415, and such that the base station may reallocate orotherwise reuse resources associated with dropped LP PUCCH 415, whichmay improve spectral efficiency, reduce latency, etc.).

FIG. 5A illustrates an example of a scheduling diagram 500 that supportstechniques for intra-UE and inter-UE cancelation of overlappingcommunications in accordance with aspects of the present disclosure. Insome examples, scheduling diagram 500 may implement aspects of wirelesscommunications system 100, wireless communications system 200,scheduling diagram 300, scheduling diagram 301, and/or schedulingdiagram 400. Scheduling diagram 500 may illustrate an example of a priorallocation knowledge scheduling constraint in accordance with aspects ofthe techniques described herein. For example, in some scenarios, a priorallocation knowledge scheduling constraint may reduce unnecessaryoverhead, avoid multiplexing and cancelation ambiguity, reducecomputational complexity at the UE, etc., and may generally provide formore efficient dynamic resource allocation within wirelesscommunications systems.

For example, a UE may receive a first grant (e.g., HP DCI 510)scheduling a first transmission (e.g., an HP uplink transmission 520).In such scenarios, according to the described prior allocation knowledgescheduling constraint, there may be only a few cases where the UE mayexpect to receive a subsequent (e.g., a second) grant (e.g., LP DCI 505)scheduling a second transmission (e.g., an LP uplink transmission 515)that overlaps with the initially scheduled HP uplink transmission 520.For instance, in cases where an HP DCI 510 is a dynamic grant for adynamic resource allocation, base station transmission of an LP DCI 505to schedule an LP uplink transmission 515 may waste overhead resourcesand may be otherwise inefficient as the UE may already be known tocancel the LP uplink transmission 515 on behalf of the overlapped HPuplink transmission 520 (e.g., which the base station may already havebeen aware of due to the earlier transmission of the HP DCI 510). Assuch, in accordance with the prior allocation knowledge schedulingconstraint, a UE may not expect to be dynamically configured to transmita low priority uplink transmission that overlaps with a previouslydynamically scheduled (e.g., dynamically configured) high priorityuplink transmission.

Generally, the prior allocation knowledge scheduling constraint mayprovide for a base station being constrained or prohibited fromscheduling a transmission that it knows will be canceled by the UE(e.g., from scheduling a low priority transmission that overlaps with apreviously dynamically configured high priority transmission). Such mayreduce unnecessary overhead (e.g., of base station signaling of LP DCI505 that will not be scheduled by a UE), reduce unnecessary decoding andpower consumption by a UE (e.g., unnecessary decoding of LP DCI 505 by aUE), etc.

As an example, in some cases, a base station may schedule a UE totransmit HARQ-ACK information in response to a PDSCH reception without acorresponding PDCCH (e.g., a semi-persistently scheduled (SPS) PDSCH),or the base station may schedule the UE to transmit a PUSCH with one ormore semi-persistent channel state information (CSI) reports. In suchcases, the UE may always transmit the HARQ-ACK information and the CSIreports, and, as such, the base station may avoid scheduling lowpriority uplink transmissions that overlap with previously scheduledhigh priority uplink transmissions. Thus, the prior allocation knowledgescheduling constraint may indicate that the UE does not expect to bescheduled for a low priority uplink transmission that overlaps with apreviously scheduled HARQ-ACK transmission or CSI transmission. In someaspects, the HARQ-ACK for SPS PDSCH and the semi-persistent CSI reportson PUSCH may be scheduled or activated by DCI (e.g., activation DCI),and the UE may not expect to receive a low priority grant after theactivation DCI (e.g., where the low priority grant schedules a lowpriority uplink transmission overlapping the HARQ-ACK or CSI reporttransmission).

However, the prior allocation knowledge scheduling constraint mayprovide for some scenarios where transmission of a low priority grantsubsequent to a high priority grant may be efficient. For example, ifthe high priority uplink transmission (e.g., HP uplink transmission 520)is not dynamically configured (e.g., is RRC configured), the basestation may transmit a low priority grant that may schedule atransmission that overlaps with the high priority uplink transmission(e.g., as the UE may or may not use the HP uplink transmission 520 whenit is not dynamically configured). For instance, in cases where HPuplink transmission 520 is a high priority SR transmission or a highpriority uplink configured grant transmission, the UE may or may nothave new data in order to use the HP uplink transmission 520. Forinstance, if the HP uplink transmission 520 is a high priority SRtransmission and the UE has no new data to transmit (e.g., if the UE hasa high priority data buffer status below some threshold), the UE mayskip or otherwise drop the HP transmission 520 regardless of whetheranother transmission is overlapping or not. As such, from the basestation perspective, the high priority transmission (e.g., HP uplinktransmission 520) may, in some cases, not be transmitted by the UE(e.g., if there is no HP data generated by the UE).

Therefore, in such scenarios where the UE is known to potentially skipthe HP uplink transmission 520 (e.g., when HP uplink transmission 520 isnot dynamically configured), the prior allocation knowledge schedulingconstraint may still allow for base station transmission of anadditional grant (e.g., LP DCI 505) that schedules a second transmissionthat at least partially overlaps with the HP uplink transmission 520. Insome cases, the UE may have HP data and may thus cancel or drop the LPuplink transmission 515. In other cases, the UE buffer status for HPdata may be below a threshold and the UE may thus perform the LP uplinktransmission 515 (e.g., and skip or cancel the HP uplink transmission520).

FIG. 5B illustrates an example of a scheduling diagram 501 that supportstechniques for intra-UE and inter-UE cancelation of overlappingcommunications in accordance with aspects of the present disclosure. Insome examples, scheduling diagram 501 may implement aspects of wirelesscommunications system 100, wireless communications system 200,scheduling diagram 300, scheduling diagram 301, scheduling diagram 400,and/or scheduling diagram 500. Scheduling diagram 501 may illustrateanother example of a prior allocation knowledge scheduling constraint inaccordance with aspects of the techniques described herein. For example,in some scenarios, a prior allocation knowledge scheduling constraintmay reduce unnecessary overhead, avoid multiplexing and cancelationambiguity, reduce computational complexity at the UE, etc., and maygenerally provide for more efficient dynamic resource allocation withinwireless communications systems.

For example, a UE may receive a PI (e.g., ULPI 525) preempting one ormore frequency-time parts. According to the prior allocation knowledgescheduling constraint described herein, the UE may not expect to bescheduled by an additional grant (e.g., HP DCI 535) that schedules aPUSCH/SRS (e.g., HP PUSCH 530) on a resource (e.g., symbols) if any partof the resource (e.g., any of the symbols) is indicated as unavailableby the previously scheduled ULPI 525. In other words, upon transmissionof ULPI 525, a base station is not expected to schedule a transmissionover any resources (e.g., or frequency-time parts) overlapping with anyof the one or more frequency-time parts indicated by the ULPI 525. Forexample, a base station may not send the scheduling grant in the samePDCCH monitoring occasion as the ULPI or after the PDCCH monitoringoccasion where the UE detects the ULPI. In other words, the base stationmay schedule the transmission prior to transmission of ULPI, but not atthe same time or after the transmission of ULPI.

Generally, the prior allocation knowledge scheduling constraint mayprovide for a base station being constrained or prohibited fromscheduling a transmission that it knows will be canceled by the UE(e.g., from scheduling a transmission that overlaps with resourcesindicated as unavailable by a previously transmitted PI). Such mayreduce unnecessary overhead (e.g., of base station signaling HP DCI 535that will not be scheduled by a UE), reduce unnecessary decoding andpower consumption by a UE (e.g., of unnecessary decoding of HP DCI 535by a UE), etc. As such, wireless communications systems may moreefficiently utilize resources (e.g., and may more efficiently conductdynamic resource allocation techniques) when implementing schedulingconstraints (e.g., such as the described prior allocation knowledgescheduling constraint).

FIG. 6 illustrates an example of a process flow 600 that supportstechniques for intra-UE and inter-UE cancelation of overlappingcommunications in accordance with aspects of the present disclosure. Insome examples, process flow 600 may implement aspects of wirelesscommunications system 100, wireless communications system 200,scheduling diagram 300, scheduling diagram 301, scheduling diagram 400,scheduling diagram 500, and/or scheduling diagram 501. Process flow 600may be implemented by a UE 115-c and a base station 105-b, which may beexamples of a UE 115 and a base station 105 described with reference toFIGS. 1-5 . In the following description of the process flow 600, theoperations between UE 115-c and base station 105-b may be transmitted ina different order than the order shown, or the operations performed bybase station 105-b and UE 115-c may be performed in different orders orat different times. Certain operations may also be left out of theprocess flow 600, or other operations may be added to the process flow600. It is to be understood that while base station 105-b and UE 115-care shown performing a number of the operations of process flow 600, anywireless device may perform the operations shown.

At 605, UE 115-c and base station 105-c may identify one or morescheduling constraints described herein. For example, wirelesscommunications systems may preconfigure or specify one or morescheduling constraints described herein.

At 610, base station 105-b may transmit an uplink allocation ofresources. For instance, base station 105-b may transmit a first grant(e.g., LP DCI, HP DCI, etc.) for a first uplink transmission (e.g., LPPUCCH, LP PUSCH, HP PUCCH, HP PUSCH, etc.) scheduled for transmission bythe UE in a first TTI (e.g., scheduled for transmission by the UE insome frequency-time resources). For instance, base station 105-b maytransmit a first grant for a low priority uplink transmission by the UEscheduled over some set of resources.

At 615, base station 105-b may determine a reallocation of uplinkresources (e.g., in accordance with one or more scheduling constraintsdescribed herein). For example, base station 105-b may determine toreallocate at least partial resources scheduled by the grant transmittedat 610. As an example, in cases where the first grant transmitted at 610is for a low priority transmission, the base station 105-b may determineto reclaim and/or reallocate the set of resources indicated by the firstgrant (e.g., to be reallocated for a high priority transmission for UE115-c, to be reallocated for a high priority transmission for adifferent UE 115, etc.).

At 620, base station 105-b may transmit a second grant and/or a PI to UE115-c based on the determination at 615. For example, in cases where theresources indicated by the first grant (at 610) are reallocated for theUE 115-c, the base station 105-b may transmit a second grant for asecond transmission (e.g., high priority transmission) that at leastpartially overlaps with the resources indicated by the first grant. Incases where the resources indicated by the first grant (at 610) arereallocated for a different UE, the base station 105-b may transmit a PI(e.g., an ULPI) indicating one or more frequency-time parts that atleast partially overlap with the resources indicated by the first grantin order to preempt the first uplink transmission and reclaim the firstset of resources by the base station 105-b.

At 625, UE 115-c may, in some scenarios, perform multiplexing and/orcanceling operations in accordance with one or more schedulingconstraints described herein.

At 630, in some cases, base station 105-b may determine a reallocationof uplink resources (e.g., in accordance with one or more schedulingconstraints described herein). For example, base station 105-b maydetermine to reallocate at least partial resources scheduled by thegrants transmitted at 610 and/or 620. As an example, the base station105-b may determine to reclaim and/or reallocate the set of resourcesindicated by the grants transmitted at 610 and/or 620 (e.g., to bereallocated for a high priority transmission for UE 115-c, to bereallocated for a high priority transmission for a different UE 115,etc.).

At 635, base station 105-b may transmit an additional grant (e.g., athird grant) or a PI to UE 115-c based on the determination at 630. Forexample, in cases where the resources indicated by the grantstransmitted at 610 and/or 620 are reallocated for the UE 115-c, the basestation 105-b may transmit an additional grant for a third transmission(e.g., an additional high priority transmission) that at least partiallyoverlaps with the resources indicated by the grants transmitted at 610and/or 620. In cases where the resources indicated by the grantstransmitted at 610 and/or 620 are reallocated for a different UE, thebase station 105-b may transmit a PI (e.g., an ULPI) indicating one ormore frequency-time parts that at least partially overlap with theresources indicated by the grants transmitted at 610 and/or 620 in orderto preempt the first and/or second uplink transmissions and reclaim theresources by the base station 105-b.

At 640, UE 115-c may, in some scenarios, perform multiplexing and/orcanceling operations in accordance with one or more schedulingconstraints described herein. At 645, UE 115-c may, in some cases,transmit uplink communications to the base station 105-b (e.g., based atleast in part on the multiplexing and/or cancelation operationsperformed at 625 and/or 640). In some cases, UE 115-c may transmit an HPPUSCH with piggybacked UCI from an HP PUCCH, the UE 115-c may transmitan LP uplink transmission, the UE may cancel all transmissions andtransmit nothing at all, etc. (e.g., as discussed in accordance with thevarious examples described herein).

As described herein, UE 115-c may perform multiplexing and/or cancelingoperations at 625 and 640 in accordance with one or more schedulingconstraints. For example, in cases where the first transmission (e.g.,scheduled by the first grant received at 610) comprises a low prioritytransmission and the second transmission (e.g., scheduled by a secondgrant received at 620) comprises a high priority transmission, the UE115-c may cancel the low priority transmission at 625 according to thecancelation determination permanency scheduling constraint describedherein (e.g., as discussed in more detail herein, for example, withreference to FIG. 3B). In cases where the base station 105-b transmitsan additional grant or PI at 635 that may result in the first and secondtransmissions no longer overlapping, the UE 115-c may maintain thedetermination (at 625) to cancel the low priority transmission (e.g., anadditional grant received at 635 may be discarded in terms of thedetermination to cancel the low priority transmission).

In other examples, in cases where the first transmission (e.g.,scheduled by the first grant received at 610) comprises a low prioritytransmission and the second transmission (e.g., scheduled by a secondgrant received at 620) comprises a high priority transmission, the UE115-c may cancel the low priority transmission at 620 according to theintra-UE/inter-UE ordering scheduling constraint described herein (e.g.,as discussed in more detail herein, for example, with reference to FIG.4 ). In cases where the base station 105-b transmits PI at 635 that maycancel the high priority transmission and result in the low prioritytransmission and high priority transmission no longer overlapping, theUE 115-c may have already canceled the low priority transmission and maysubsequently cancel the high priority transmission as preempted inaccordance with the intra-UE/inter-UE ordering scheduling constraint.

As yet another example, at 605, 615, and 630, base station 105-b maygenerally adhere to the one or more scheduling constraints describedherein. For example, prior allocation knowledge scheduling constraintsdescribed herein (e.g., with reference to FIGS. 5A and 5B) may providefor base station 105-b being constrained or prohibited from schedulingsome transmissions that base station 105-b knows will be canceled by theUE 115-c (e.g., from scheduling a low priority transmission thatoverlaps with a previously dynamically configured high prioritytransmission). Such may reduce unnecessary overhead (e.g., of basestation 105-b signaling of grants for transmissions that will not bescheduled by a UE 115-c), reduce unnecessary decoding and powerconsumption by a UE 115-c, etc.

FIG. 7 shows a block diagram 700 of a device 705 that supportstechniques for intra-UE and inter-UE cancelation of overlappingcommunications in accordance with aspects of the present disclosure. Thedevice 705 may be an example of aspects of a UE 115 as described herein.The device 705 may include a receiver 710, a communications manager 715,and a transmitter 720. The device 705 may also include a processor. Eachof these components may be in communication with one another (e.g., viaone or more buses).

The receiver 710 may receive information such as packets, user data, orcontrol information associated with various information channels (e.g.,control channels, data channels, and information related to techniquesfor intra-UE and inter-UE cancelation of overlapping communications,etc.). Information may be passed on to other components of the device705. The receiver 710 may be an example of aspects of the transceiver1020 described with reference to FIG. 10 . The receiver 710 may utilizea single antenna or a set of antennas.

The communications manager 715 may receive a first grant for a firstuplink transmission scheduled for transmission by the UE, identify thatthe first uplink transmission at least partially overlaps with a seconduplink transmission also scheduled for transmission by the UE, determineto drop the second uplink transmission based on a first schedulingconstraint to resolve overlapping between the first uplink transmissionand the second uplink transmission, where the first schedulingconstraint is based at least in part on a first priority of the firstuplink transmission being greater than a second priority of the seconduplink transmission, and transmit uplink data transmissions inaccordance with a second scheduling constraint, where the secondscheduling constraint relates to an additional uplink transmissionscheduled by an additional grant received after the first grant andscheduled to at least partially overlap with the first uplinktransmission, and where the second scheduling constraint is evaluatedafter satisfaction of the first scheduling constraint to resolveoverlapping between the additional uplink transmission and the firstuplink transmission after resolving overlapping between the first uplinktransmission and the second uplink transmission.

The communications manager 715 may also identify that a first uplinktransmission scheduled for transmission by the UE at least partiallyoverlaps with a second uplink transmission also scheduled fortransmission by the UE, receive an uplink cancelation indication for afrequency-time resource that at least partially overlaps with the firstuplink transmission, determine to drop the second uplink transmissionbased on a scheduling constraint to resolve overlapping between thefirst uplink transmission and the second uplink transmission, where thescheduling constraint is based at least in part on a first priority ofthe first uplink transmission being greater than a second priority ofthe second uplink transmission, and apply the uplink cancelationindication to the first uplink transmission after determining that thescheduling constraint is satisfied.

The communications manager 715 may also receive a first grant for afirst uplink transmission scheduled for transmission by the UE, receive,after receipt of the first grant, a second grant for a second uplinktransmission scheduled for transmission by the UE, determine that thefirst uplink transmission and the second uplink transmission arescheduled so as to satisfy a scheduling constraint that is based on afirst priority of the first uplink transmission being greater than asecond priority of the second uplink transmission, the schedulingconstraint further based on whether the first uplink transmissionoverlaps with the second uplink transmission, and transmit the firstuplink transmission or the second uplink transmission based onsatisfaction of the scheduling constraint.

The communications manager 715 may also receive an uplink cancelationindication for a first frequency-time resource, receive, after receiptof the uplink cancelation indication, a grant for an uplink transmissionscheduled for transmission by the UE in a second frequency-timeresource, determine that the uplink transmission is scheduled so as tosatisfy a scheduling constraint that is based on whether the firstfrequency-time resource overlaps with the second frequency-timeresource, and determine to preempt the first frequency-time resource andtransmit the uplink transmission based on satisfaction of the schedulingconstraint.

The communications manager 715 may be an example of aspects of thecommunications manager 1010 described herein. The communications manager715, or its sub-components, may be implemented in hardware, code (e.g.,software or firmware) executed by a processor, or any combinationthereof. If implemented in code executed by a processor, the functionsof the communications manager 715, or its sub-components may be executedby a general-purpose processor, a digital signal processor (DSP), anapplication-specific integrated circuit (ASIC), a field-programmablegate array (FPGA) or other programmable logic device, discrete gate ortransistor logic, discrete hardware components, or any combinationthereof designed to perform the functions described in the presentdisclosure.

The communications manager 715, or its sub-components, may be physicallylocated at various positions, including being distributed such thatportions of functions are implemented at different physical locations byone or more physical components. In some examples, the communicationsmanager 715, or its sub-components, may be a separate and distinctcomponent in accordance with various aspects of the present disclosure.In some examples, the communications manager 715, or its sub-components,may be combined with one or more other hardware components, includingbut not limited to an input/output (I/O) component, a transceiver, anetwork server, another computing device, one or more other componentsdescribed in the present disclosure, or a combination thereof inaccordance with various aspects of the present disclosure.

The transmitter 720 may transmit signals generated by other componentsof the device 705. In some examples, the transmitter 720 may becollocated with a receiver 710 in a transceiver module. For example, thetransmitter 720 may be an example of aspects of the transceiver 1020described with reference to FIG. 10 . The transmitter 720 may utilize asingle antenna or a set of antennas.

FIG. 8 shows a block diagram 800 of a device 805 that supportstechniques for intra-UE and inter-UE cancelation of overlappingcommunications in accordance with aspects of the present disclosure. Thedevice 805 may be an example of aspects of a device 705, or a UE 115 asdescribed herein. The device 805 may include a receiver 810, acommunications manager 815, and a transmitter 840. The device 805 mayalso include a processor. Each of these components may be incommunication with one another (e.g., via one or more buses).

The receiver 810 may receive information such as packets, user data, orcontrol information associated with various information channels (e.g.,control channels, data channels, and information related to techniquesfor intra-UE and inter-UE cancelation of overlapping communications,etc.). Information may be passed on to other components of the device805. The receiver 810 may be an example of aspects of the transceiver1020 described with reference to FIG. 10 . The receiver 810 may utilizea single antenna or a set of antennas.

The communications manager 815 may be an example of aspects of thecommunications manager 715 as described herein. The communicationsmanager 815 may include a grant manager 820, a scheduling manager 825, ascheduling constraint manager 830, and a transmission manager 835. Thecommunications manager 815 may be an example of aspects of thecommunications manager 1010 described herein.

The grant manager 820 may receive a first grant for a first uplinktransmission scheduled for transmission by the UE. The schedulingmanager 825 may identify that the first uplink transmission at leastpartially overlaps with a second uplink transmission also scheduled fortransmission by the UE. The scheduling constraint manager 830 maydetermine to drop the second uplink transmission based on a firstscheduling constraint to resolve overlapping between the first uplinktransmission and the second uplink transmission, where the firstscheduling constraint is based at least in part on a first priority ofthe first uplink transmission being greater than a second priority ofthe second uplink transmission. The transmission manager 835 maytransmit uplink data transmissions in accordance with a secondscheduling constraint, where the second scheduling constraint relates toan additional uplink transmission scheduled by an additional grantreceived after the first grant and scheduled to at least partiallyoverlap with the first uplink transmission, and where the secondscheduling constraint is evaluated after satisfaction of the firstscheduling constraint to resolve overlapping between the additionaluplink transmission and the first uplink transmission after resolvingoverlapping between the first uplink transmission and the second uplinktransmission.

The scheduling manager 825 may identify that a first uplink transmissionscheduled for transmission by the UE at least partially overlaps with asecond uplink transmission also scheduled for transmission by the UE.The scheduling manager 825 may receive an uplink cancelation indicationfor a frequency-time resource that at least partially overlaps with thefirst uplink transmission. The scheduling constraint manager 830 maydetermine to drop the second uplink transmission based on a schedulingconstraint to resolve overlapping between the first uplink transmissionand the second uplink transmission, where the scheduling constraint isbased at least in part on a first priority of the first uplinktransmission being greater than a second priority of the second uplinktransmission and apply the uplink cancelation indication to the firstuplink transmission after determining that the scheduling constraint issatisfied.

The grant manager 820 may receive a first grant for a first uplinktransmission scheduled for transmission by the UE and receive, afterreceipt of the first grant, a second grant for a second uplinktransmission scheduled for transmission by the UE. The schedulingconstraint manager 830 may determine that the first uplink transmissionand the second uplink transmission are scheduled so as to satisfy ascheduling constraint that is based on a first priority of the firstuplink transmission being greater than a second priority of the seconduplink transmission, the scheduling constraint further based on whetherthe first uplink transmission overlaps with the second uplinktransmission. The transmission manager 835 may transmit the first uplinktransmission or the second uplink transmission based on satisfaction ofthe scheduling constraint.

The scheduling manager 825 may receive an uplink cancelation indicationfor a first frequency-time resource. The grant manager 820 may receive,after receipt of the uplink cancelation indication, a grant for anuplink transmission scheduled for transmission by the UE in a secondfrequency-time resource. The scheduling constraint manager 830 maydetermine that the uplink transmission is scheduled so as to satisfy ascheduling constraint that is based on whether the first frequency-timeresource overlaps with the second frequency-time resource and determineto preempt the first frequency-time resource and transmit the uplinktransmission based on satisfaction of the scheduling constraint.

The transmitter 840 may transmit signals generated by other componentsof the device 805. In some examples, the transmitter 840 may becollocated with a receiver 810 in a transceiver module. For example, thetransmitter 840 may be an example of aspects of the transceiver 1020described with reference to FIG. 10 . The transmitter 840 may utilize asingle antenna or a set of antennas.

FIG. 9 shows a block diagram 900 of a communications manager 905 thatsupports techniques for intra-UE and inter-UE cancelation of overlappingcommunications in accordance with aspects of the present disclosure. Thecommunications manager 905 may be an example of aspects of acommunications manager 715, a communications manager 815, or acommunications manager 1010 described herein. The communications manager905 may include a grant manager 910, a scheduling manager 915, ascheduling constraint manager 920, a transmission manager 925, apiggybacking manager 930, and an UE buffer manager 935. Each of thesemodules may communicate, directly or indirectly, with one another (e.g.,via one or more buses).

The grant manager 910 may receive a first grant for a first uplinktransmission scheduled for transmission by the UE. The schedulingmanager 915 may identify that the first uplink transmission at leastpartially overlaps with a second uplink transmission also scheduled fortransmission by the UE. The scheduling constraint manager 920 maydetermine to drop the second uplink transmission based on a firstscheduling constraint to resolve overlapping between the first uplinktransmission and the second uplink transmission, where the firstscheduling constraint is based at least in part on a first priority ofthe first uplink transmission being greater than a second priority ofthe second uplink transmission. The transmission manager 925 maytransmit uplink data transmissions in accordance with a secondscheduling constraint, where the second scheduling constraint relates toan additional uplink transmission scheduled by an additional grantreceived after the first grant and scheduled to at least partiallyoverlap with the first uplink transmission, and where the secondscheduling constraint is evaluated after satisfaction of the firstscheduling constraint to resolve overlapping between the additionaluplink transmission and the first uplink transmission after resolvingoverlapping between the first uplink transmission and the second uplinktransmission.

In some examples, the grant manager 910 may receive the additionalgrant. In some examples, the scheduling constraint manager 920 mayignore the received additional grant based on the second schedulingconstraint until overlapping between the first uplink transmission andthe second uplink transmission is received, where the second uplinktransmission is dropped based on the ignoring. In some examples, thegrant manager 910 may receive the additional grant for the additionaluplink transmission scheduled for transmission by the UE. In someexamples, the scheduling constraint manager 920 may determine to dropthe first uplink transmission based on the additional uplinktransmission at least partially overlapping with the first uplinktransmission, where the second uplink transmission and the additionaluplink transmission are non-overlapping.

The piggybacking manager 930 may piggyback at least a portion of thefirst uplink transmission on to the additional uplink transmission basedon the determination to drop the first uplink transmission. In someexamples, the transmission manager 925 may transmit the additionaluplink transmission and the piggybacked portion of the first uplinktransmission, where the determination to drop the second uplinktransmission is maintained based on the second scheduling constraint.

In some cases, the first uplink transmission includes a high priorityuplink control channel transmission or a high priority uplink sharedchannel transmission. In some cases, the second uplink transmissionincludes a low priority uplink control channel transmission, a lowpriority uplink shared channel transmission, or a sounding referencesignal transmission. In some cases, the additional uplink transmissionincludes an additional high priority uplink transmission. In some cases,the additional grant includes a group-common grant, an uplinkcancelation indication, or a slot format indicator.

In some aspects, the scheduling manager 915 may identify that a firstuplink transmission scheduled for transmission by the UE at leastpartially overlaps with a second uplink transmission also scheduled fortransmission by the UE. In some examples, the scheduling manager 915 mayreceive an uplink cancelation indication for a frequency-time resourcethat at least partially overlaps with the first uplink transmission. Insome examples, the scheduling constraint manager 920 may determine todrop the second uplink transmission based on a scheduling constraint toresolve overlapping between the first uplink transmission and the seconduplink transmission, where the scheduling constraint is based at leastin part on a first priority of the first uplink transmission beinggreater than a second priority of the second uplink transmission. Insome examples, the scheduling constraint manager 920 may apply theuplink cancelation indication to the first uplink transmission afterdetermining that the scheduling constraint is satisfied.

In some examples, the scheduling constraint manager 920 may determine todrop the first uplink transmission based on the frequency-time resourceat least partially overlapping with the first uplink transmission. Insome examples, the scheduling constraint manager 920 may determine totransmit the first uplink transmission even though the frequency-timeresource at least partially overlaps with the first uplink transmission.In some cases, the first uplink transmission includes a high priorityuplink control channel transmission or a high priority uplink sharedchannel transmission. In some cases, the second uplink transmissionincludes a low priority uplink control channel transmission, a lowpriority uplink shared channel transmission, or a sounding referencesignal transmission.

In some aspects, the grant manager 910 may receive a first grant for afirst uplink transmission scheduled for transmission by the UE. In someexamples, the grant manager 910 may receive, after receipt of the firstgrant, a second grant for a second uplink transmission scheduled fortransmission by the UE. In some examples, the scheduling constraintmanager 920 may determine that the first uplink transmission and thesecond uplink transmission are scheduled so as to satisfy a schedulingconstraint that is based on a first priority of the first uplinktransmission being greater than a second priority of the second uplinktransmission, the scheduling constraint further based on whether thefirst uplink transmission overlaps with the second uplink transmission.In some examples, the transmission manager 925 may transmit the firstuplink transmission or the second uplink transmission based onsatisfaction of the scheduling constraint.

In some examples, the transmission manager 925 may transmit the firstuplink transmission. The UE buffer manager 935 may identify that the UEhas data to be included in the first uplink transmission, where thefirst uplink transmission is transmitted based on the UE having data tobe included in the first uplink transmission. In some examples, thescheduling constraint manager 920 may discard the received second grantbased on the scheduling constraint, where the first uplink transmissionis transmitted based on the discarding. In some cases, the first grantincludes a dynamic high priority grant. In some examples, thetransmission manager 925 may transmit the second uplink transmission.

In some examples, the UE buffer manager 935 may determine to skip thefirst uplink transmission based on a buffer status of the UE being belowa threshold, where the second uplink transmission is transmitted basedon the determination to skip the first uplink transmission. In somecases, the first uplink transmission includes a high priority schedulingrequest or a high priority uplink configured grant transmission. In somecases, the scheduling constraint is satisfied based on the first uplinktransmission and the second uplink transmission being non-overlapping.In some cases, the first uplink transmission comprises a hybridautomatic repeat request acknowledgment transmission or a channel stateinformation transmission. In some cases, the scheduling constraintprovides that the UE does not expect to receive a grant scheduling a lowpriority uplink transmission that overlaps with a previously scheduledhigh priority uplink transmission.

In some aspects, the scheduling manager 915 may receive an uplinkcancelation indication for a first frequency-time resource. In someexamples, the grant manager 910 may receive, after receipt of the uplinkcancelation indication, a grant for an uplink transmission scheduled fortransmission by the UE in a second frequency-time resource. In someexamples, the scheduling constraint manager 920 may determine that theuplink transmission is scheduled so as to satisfy a schedulingconstraint that is based on whether the first frequency-time resourceoverlaps with the second frequency-time resource. In some examples, thescheduling constraint manager 920 may determine to preempt the firstfrequency-time resource and transmit the uplink transmission based onsatisfaction of the scheduling constraint.

In some cases, the scheduling constraint is satisfied based on the firstfrequency-time resource being entirely separate in time and frequencythan the second frequency-time resource.

FIG. 10 shows a diagram of a system 1000 including a device 1005 thatsupports techniques for intra-UE and inter-UE cancelation of overlappingcommunications in accordance with aspects of the present disclosure. Thedevice 1005 may be an example of or include the components of device705, device 805, or a UE 115 as described herein. The device 1005 mayinclude components for bi-directional voice and data communicationsincluding components for transmitting and receiving communications,including a communications manager 1010, an I/O controller 1015, atransceiver 1020, an antenna 1025, memory 1030, and a processor 1040.These components may be in electronic communication via one or morebuses (e.g., bus 1045).

The communications manager 1010 may receive a first grant for a firstuplink transmission scheduled for transmission by the UE, identify thatthe first uplink transmission at least partially overlaps with a seconduplink transmission also scheduled for transmission by the UE, determineto drop the second uplink transmission based on a first schedulingconstraint to resolve overlapping between the first uplink transmissionand the second uplink transmission, where the first schedulingconstraint is based at least in part on a first priority of the firstuplink transmission being greater than a second priority of the seconduplink transmission, and transmit uplink data transmissions inaccordance with a second scheduling constraint, where the secondscheduling constraint relates to an additional uplink transmissionscheduled by an additional grant received after the first grant andscheduled to at least partially overlap with the first uplinktransmission, and where the second scheduling constraint is evaluatedafter satisfaction of the first scheduling constraint to resolveoverlapping between the additional uplink transmission and the firstuplink transmission after resolving overlapping between the first uplinktransmission and the second uplink transmission.

The communications manager 1010 may also identify that a first uplinktransmission scheduled for transmission by the UE at least partiallyoverlaps with a second uplink transmission also scheduled fortransmission by the UE, receive an uplink cancelation indication for afrequency-time resource that at least partially overlaps with the firstuplink transmission, determine to drop the second uplink transmissionbased on a scheduling constraint to resolve overlapping between thefirst uplink transmission and the second uplink transmission, where thescheduling constraint is based at least in part on a first priority ofthe first uplink transmission being greater than a second priority ofthe second uplink transmission, and apply the uplink cancelationindication to the first uplink transmission after determining that thescheduling constraint is satisfied.

The communications manager 1010 may also receive a first grant for afirst uplink transmission scheduled for transmission by the UE, receive,after receipt of the first grant, a second grant for a second uplinktransmission scheduled for transmission by the UE, determine that thefirst uplink transmission and the second uplink transmission arescheduled so as to satisfy a scheduling constraint that is based on afirst priority of the first uplink transmission being greater than asecond priority of the second uplink transmission, the schedulingconstraint further based on whether the first uplink transmissionoverlaps with the second uplink transmission, and transmit the firstuplink transmission or the second uplink transmission based onsatisfaction of the scheduling constraint.

The communications manager 1010 may also receive an uplink cancelationindication for a first frequency-time resource, receive, after receiptof the uplink cancelation indication, a grant for an uplink transmissionscheduled for transmission by the UE in a second frequency-timeresource, determine that the uplink transmission is scheduled so as tosatisfy a scheduling constraint that is based on whether the firstfrequency-time resource overlaps with the second frequency-timeresource, and determine to preempt the first frequency-time resource andtransmit the uplink transmission based on satisfaction of the schedulingconstraint.

The I/O controller 1015 may manage input and output signals for thedevice 1005. The I/O controller 1015 may also manage peripherals notintegrated into the device 1005. In some cases, the I/O controller 1015may represent a physical connection or port to an external peripheral.In some cases, the I/O controller 1015 may utilize an operating systemsuch as iOS®, ANDROID®, MS-DOS®, MS-WINDOWS®, OS/2®, UNIX®, LINUX®, oranother known operating system. In other cases, the I/O controller 1015may represent or interact with a modem, a keyboard, a mouse, atouchscreen, or a similar device. In some cases, the I/O controller 1015may be implemented as part of a processor. In some cases, a user mayinteract with the device 1005 via the I/O controller 1015 or viahardware components controlled by the I/O controller 1015.

The transceiver 1020 may communicate bi-directionally, via one or moreantennas, wired, or wireless links as described above. For example, thetransceiver 1020 may represent a wireless transceiver and maycommunicate bi-directionally with another wireless transceiver. Thetransceiver 1020 may also include a modem to modulate the packets andprovide the modulated packets to the antennas for transmission, and todemodulate packets received from the antennas.

In some cases, the wireless device may include a single antenna 1025.However, in some cases the device may have more than one antenna 1025,which may be capable of concurrently transmitting or receiving multiplewireless transmissions.

The memory 1030 may include RAM and ROM. The memory 1030 may storecomputer-readable, computer-executable code or software 1035 includinginstructions that, when executed, cause the processor to perform variousfunctions described herein. In some cases, the memory 1030 may contain,among other things, a basic input/output system (BIOS) which may controlbasic hardware or software operation such as the interaction withperipheral components or devices.

The processor 1040 may include an intelligent hardware device, (e.g., ageneral-purpose processor, a DSP, a CPU, a microcontroller, an ASIC, anFPGA, a programmable logic device, a discrete gate or transistor logiccomponent, a discrete hardware component, or any combination thereof).In some cases, the processor 1040 may be configured to operate a memoryarray using a memory controller. In other cases, a memory controller maybe integrated into the processor 1040. The processor 1040 may beconfigured to execute computer-readable instructions stored in a memory(e.g., the memory 1030) to cause the device 1005 to perform variousfunctions (e.g., functions or tasks supporting techniques for intra-UEand inter-UE cancelation of overlapping communications).

The software 1035 may include instructions to implement aspects of thepresent disclosure, including instructions to support wirelesscommunications. The software 1035 may be stored in a non-transitorycomputer-readable medium such as system memory or other type of memory.In some cases, the software 1035 may not be directly executable by theprocessor 1040 but may cause a computer (e.g., when compiled andexecuted) to perform functions described herein.

FIG. 11 shows a block diagram 1100 of a device 1105 that supportstechniques for intra-UE and inter-UE cancelation of overlappingcommunications in accordance with aspects of the present disclosure. Thedevice 1105 may be an example of aspects of a base station 105 asdescribed herein. The device 1105 may include a receiver 1110, acommunications manager 1115, and a transmitter 1120. The device 1105 mayalso include a processor. Each of these components may be incommunication with one another (e.g., via one or more buses).

The receiver 1110 may receive information such as packets, user data, orcontrol information associated with various information channels (e.g.,control channels, data channels, and information related to techniquesfor intra-UE and inter-UE cancelation of overlapping communications,etc.). Information may be passed on to other components of the device1105. The receiver 1110 may be an example of aspects of the transceiver1420 described with reference to FIG. 14 . The receiver 1110 may utilizea single antenna or a set of antennas.

The communications manager 1115 may transmit a first grant for a firstuplink transmission scheduled for transmission by a UE, identify thatthe first uplink transmission at least partially overlaps with a seconduplink transmission also scheduled for transmission by the UE, determinethe second uplink transmission will be dropped by the UE based on afirst scheduling constraint to resolve overlapping between the firstuplink transmission and the second uplink transmission, where the firstscheduling constraint is based at least in part on a first priority ofthe first uplink transmission being greater than a second priority ofthe second uplink transmission, and transmit, after the first grant, anadditional grant in accordance with a second scheduling constraint,where the second scheduling constraint relates to an additional uplinktransmission scheduled by the additional grant and scheduled to at leastpartially overlap with the first uplink transmission, and where thesecond scheduling constraint is evaluated after satisfaction of thefirst scheduling constraint to resolve overlapping between theadditional uplink transmission and the first uplink transmission afterresolving overlapping between the first uplink transmission and thesecond uplink transmission.

The communications manager 1115 may also identify that a first uplinktransmission scheduled for transmission by a UE at least partiallyoverlaps with a second uplink transmission also scheduled fortransmission by the UE, transmit an uplink cancelation indication for afrequency-time resource that at least partially overlaps with the firstuplink transmission, the second uplink transmission, or both, determinethe second uplink transmission will be dropped by the UE based on afirst scheduling constraint to resolve overlapping between the firstuplink transmission and the second uplink transmission, where the firstscheduling constraint is based at least in part on a first priority ofthe first uplink transmission being greater than a second priority ofthe second uplink transmission, and receive the first uplinktransmission in accordance with a second scheduling constraint, wherethe second scheduling constraint is evaluated after satisfaction of thefirst scheduling constraint, and where the second scheduling constraintrelates to the frequency-time resource at least partially overlappingwith the first uplink transmission, the second uplink transmission, orboth.

The communications manager 1115 may also transmit a first grant for afirst uplink transmission scheduled for transmission by a UE, transmit,after the first grant, the second grant in accordance with thescheduling constraint, and identify a scheduling constraint based on afirst priority of the first uplink transmission being greater than asecond priority of a second uplink transmission to be scheduled by asecond grant transmitted after the first grant.

The communications manager 1115 may also transmit, to a UE, an uplinkcancelation indication for a first frequency-time resource, identify ascheduling constraint that is based on whether the first frequency-timeresource overlaps with a second frequency-time resource of an uplinktransmission to be scheduled by a grant, and transmit, aftertransmission of the uplink cancelation indication, the grant for theuplink transmission in accordance with the scheduling constraint.

The communications manager 1115 may be an example of aspects of thecommunications manager 1410 described herein. The communications manager1115, or its sub-components, may be implemented in hardware, code (e.g.,software or firmware) executed by a processor, or any combinationthereof. If implemented in code executed by a processor, the functionsof the communications manager 1115, or its sub-components may beexecuted by a general-purpose processor, a DSP, an application-specificintegrated circuit (ASIC), a FPGA or other programmable logic device,discrete gate or transistor logic, discrete hardware components, or anycombination thereof designed to perform the functions described in thepresent disclosure.

The communications manager 1115, or its sub-components, may bephysically located at various positions, including being distributedsuch that portions of functions are implemented at different physicallocations by one or more physical components. In some examples, thecommunications manager 1115, or its sub-components, may be a separateand distinct component in accordance with various aspects of the presentdisclosure. In some examples, the communications manager 1115, or itssub-components, may be combined with one or more other hardwarecomponents, including but not limited to an input/output (I/O)component, a transceiver, a network server, another computing device,one or more other components described in the present disclosure, or acombination thereof in accordance with various aspects of the presentdisclosure.

The transmitter 1120 may transmit signals generated by other componentsof the device 1105. In some examples, the transmitter 1120 may becollocated with a receiver 1110 in a transceiver module. For example,the transmitter 1120 may be an example of aspects of the transceiver1420 described with reference to FIG. 14 . The transmitter 1120 mayutilize a single antenna or a set of antennas.

FIG. 12 shows a block diagram 1200 of a device 1205 that supportstechniques for intra-UE and inter-UE cancelation of overlappingcommunications in accordance with aspects of the present disclosure. Thedevice 1205 may be an example of aspects of a device 1105, or a basestation 105 as described herein. The device 1205 may include a receiver1210, a communications manager 1215, and a transmitter 1240. The device1205 may also include a processor. Each of these components may be incommunication with one another (e.g., via one or more buses).

The receiver 1210 may receive information such as packets, user data, orcontrol information associated with various information channels (e.g.,control channels, data channels, and information related to techniquesfor intra-UE and inter-UE cancelation of overlapping communications,etc.). Information may be passed on to other components of the device1205. The receiver 1210 may be an example of aspects of the transceiver1420 described with reference to FIG. 14 . The receiver 1210 may utilizea single antenna or a set of antennas.

The communications manager 1215 may be an example of aspects of thecommunications manager 1115 as described herein. The communicationsmanager 1215 may include a grant manager 1220, a scheduling manager1225, a scheduling constraint manager 1230, and an UE transmissionmanager 1235. The communications manager 1215 may be an example ofaspects of the communications manager 1410 described herein.

The grant manager 1220 may transmit a first grant for a first uplinktransmission scheduled for transmission by a UE. The scheduling manager1225 may identify that the first uplink transmission at least partiallyoverlaps with a second uplink transmission also scheduled fortransmission by the UE. The scheduling constraint manager 1230 maydetermine the second uplink transmission will be dropped by the UE basedon a first scheduling constraint to resolve overlapping between thefirst uplink transmission and the second uplink transmission, where thefirst scheduling constraint is based at least in part on a firstpriority of the first uplink transmission being greater than a secondpriority of the second uplink transmission. The grant manager 1220 maytransmit, after the first grant, an additional grant in accordance witha second scheduling constraint, where the second scheduling constraintrelates to an additional uplink transmission scheduled by the additionalgrant and scheduled to at least partially overlap with the first uplinktransmission, and where the second scheduling constraint is evaluatedafter satisfaction of the first scheduling constraint to resolveoverlapping between the additional uplink transmission and the firstuplink transmission after resolving overlapping between the first uplinktransmission and the second uplink transmission.

The scheduling manager 1225 may identify that a first uplinktransmission scheduled for transmission by a UE at least partiallyoverlaps with a second uplink transmission also scheduled fortransmission by the UE. The scheduling manager 1225 may transmit anuplink cancelation indication for a frequency-time resource that atleast partially overlaps with the first uplink transmission, the seconduplink transmission, or both. The scheduling constraint manager 1230 maydetermine the second uplink transmission will be dropped by the UE basedon a first scheduling constraint to resolve overlapping between thefirst uplink transmission and the second uplink transmission, where thefirst scheduling constraint is based at least in part on a firstpriority of the first uplink transmission being greater than a secondpriority of the second uplink transmission. The UE transmission manager1235 may receive the first uplink transmission in accordance with asecond scheduling constraint, where the second scheduling constraint isevaluated after satisfaction of the first scheduling constraint, andwhere the second scheduling constraint relates to the frequency-timeresource at least partially overlapping with the first uplinktransmission, the second uplink transmission, or both.

The grant manager 1220 may transmit a first grant for a first uplinktransmission scheduled for transmission by a UE. The schedulingconstraint manager 1230 may identify a scheduling constraint based on afirst priority of the first uplink transmission being greater than asecond priority of a second uplink transmission to be scheduled by asecond grant transmitted after the first grant. The grant manager 1220may transmit, after the first grant, the second grant in accordance withthe scheduling constraint.

The scheduling manager 1225 may transmit, to a UE, an uplink cancelationindication for a first frequency-time resource. The schedulingconstraint manager 1230 may identify a scheduling constraint that isbased on whether the first frequency-time resource overlaps with asecond frequency-time resource of an uplink transmission to be scheduledby a grant. The grant manager 1220 may transmit, after transmission ofthe uplink cancelation indication, the grant for the uplink transmissionin accordance with the scheduling constraint.

The transmitter 1240 may transmit signals generated by other componentsof the device 1205. In some examples, the transmitter 1240 may becollocated with a receiver 1210 in a transceiver module. For example,the transmitter 1240 may be an example of aspects of the transceiver1420 described with reference to FIG. 14 . The transmitter 1240 mayutilize a single antenna or a set of antennas.

FIG. 13 shows a block diagram 1300 of a communications manager 1305 thatsupports techniques for intra-UE and inter-UE cancelation of overlappingcommunications in accordance with aspects of the present disclosure. Thecommunications manager 1305 may be an example of aspects of acommunications manager 1115, a communications manager 1215, or acommunications manager 1410 described herein. The communications manager1305 may include a grant manager 1310, a scheduling manager 1315, ascheduling constraint manager 1320, a piggybacking manager 1325, and anUE transmission manager 1330. Each of these modules may communicate,directly or indirectly, with one another (e.g., via one or more buses).

The grant manager 1310 may transmit a first grant for a first uplinktransmission scheduled for transmission by a UE. The scheduling manager1315 may identify that the first uplink transmission at least partiallyoverlaps with a second uplink transmission also scheduled fortransmission by the UE. The scheduling constraint manager 1320 maydetermine the second uplink transmission will be dropped by the UE basedon a first scheduling constraint to resolve overlapping between thefirst uplink transmission and the second uplink transmission, where thefirst scheduling constraint is based at least in part on a firstpriority of the first uplink transmission being greater than a secondpriority of the second uplink transmission. In some examples, the grantmanager 1310 may transmit, after the first grant, an additional grant inaccordance with a second scheduling constraint, where the secondscheduling constraint relates to an additional uplink transmissionscheduled by the additional grant and scheduled to at least partiallyoverlap with the first uplink transmission, and where the secondscheduling constraint is evaluated after satisfaction of the firstscheduling constraint to resolve overlapping between the additionaluplink transmission and the first uplink transmission after resolvingoverlapping between the first uplink transmission and the second uplinktransmission.

In some examples, the scheduling constraint manager 1320 may determinethe transmitted additional grant will be ignored by the UE based on thesecond scheduling constraint until overlapping between the first uplinktransmission and the second uplink transmission is resolved, where thesecond uplink transmission is dropped based on the ignoring. In someexamples, the scheduling manager 1315 may determine the first uplinktransmission will be dropped by the UE based on transmitting theadditional grant. The piggybacking manager 1325 may receive theadditional uplink transmission and a piggybacked portion of the firstuplink transmission. In some cases, the first uplink transmissionincludes a high priority uplink control channel transmission or a highpriority uplink shared channel transmission. In some cases, the seconduplink transmission includes a low priority uplink control channeltransmission, a low priority uplink shared channel transmission, or asounding reference signal transmission. In some cases, the additionaluplink transmission includes an additional high priority uplinktransmission. In some cases, the additional grant includes agroup-common grant, an uplink cancelation indication, or a slot formatindicator.

In some aspects, the scheduling manager 1315 may identify that a firstuplink transmission scheduled for transmission by a UE at leastpartially overlaps with a second uplink transmission also scheduled fortransmission by the UE. In some examples, the scheduling manager 1315may transmit an uplink cancelation indication for a frequency-timeresource that at least partially overlaps with the first uplinktransmission, the second uplink transmission, or both. In some examples,the scheduling constraint manager 1320 may determine the second uplinktransmission will be dropped by the UE based on a first schedulingconstraint to resolve overlapping between the first uplink transmissionand the second uplink transmission, where the first schedulingconstraint is based at least in part on a first priority of the firstuplink transmission being greater than a second priority of the seconduplink transmission. The UE transmission manager 1330 may receive thefirst uplink transmission in accordance with a second schedulingconstraint, where the second scheduling constraint is evaluated aftersatisfaction of the first scheduling constraint, and where the secondscheduling constraint relates to the frequency-time resource at leastpartially overlapping with the first uplink transmission, the seconduplink transmission, or both.

In some examples, the scheduling constraint manager 1320 may determinethe first uplink transmission will be dropped by the UE based on thefrequency-time resource at least partially overlapping with the firstuplink transmission. In some examples, the UE transmission manager 1330may receive the first uplink transmission based on the frequency-timeresource at least partially overlapping with the second uplinktransmission. In some cases, the first uplink transmission includes ahigh priority uplink control channel transmission or a high priorityuplink shared channel transmission. In some cases, the second uplinktransmission includes a low priority uplink control channeltransmission, a low priority uplink shared channel transmission, or asounding reference signal transmission.

In some aspects, the grant manager 1310 may transmit a first grant for afirst uplink transmission scheduled for transmission by a UE. In someexamples, the scheduling constraint manager 1320 may identify ascheduling constraint based on a first priority of the first uplinktransmission being greater than a second priority of a second uplinktransmission to be scheduled by a second grant transmitted after thefirst grant. In some examples, the grant manager 1310 may transmit,after the first grant, the second grant in accordance with thescheduling constraint.

In some examples, the UE transmission manager 1330 may receive the firstuplink transmission based on the transmitted first grant. In some cases,the first grant includes a dynamic high priority grant. In someexamples, the UE transmission manager 1330 may receive the second uplinktransmission based on the transmitted additional grant. In some cases,the first uplink transmission includes a high priority schedulingrequest or a high priority uplink configured grant transmission.

In some examples, the scheduling constraint manager 1320 may determinethe UE skipped the first uplink transmission based on receiving thesecond uplink transmission, where the determination that the UE skippedthe first uplink transmission is based on a buffer status of the UEbeing below a threshold. In some cases, the scheduling constraintfurther relates to the second uplink transmission scheduled to overlapwith the first uplink transmission.

In some cases, the first uplink transmission comprises a hybridautomatic repeat request acknowledgment transmission or a channel stateinformation transmission. In some cases, the scheduling constraintprovides that the UE does not expect to receive a grant scheduling a lowpriority uplink transmission that overlaps with a previously scheduledhigh priority uplink transmission.

In some aspects, the scheduling manager 1315 may transmit, to a UE, anuplink cancelation indication for a first frequency-time resource. Insome examples, the scheduling constraint manager 1320 may identify ascheduling constraint that is based on whether the first frequency-timeresource overlaps with a second frequency-time resource of an uplinktransmission to be scheduled by a grant. In some examples, the grantmanager 1310 may transmit, after transmission of the uplink cancelationindication, the grant for the uplink transmission in accordance with thescheduling constraint.

In some cases, the scheduling constraint is satisfied based on the firstfrequency-time resource being entirely separate in time and frequencythan the second frequency-time resource.

FIG. 14 shows a diagram of a system 1400 including a device 1405 thatsupports techniques for intra-UE and inter-UE cancelation of overlappingcommunications in accordance with aspects of the present disclosure. Thedevice 1405 may be an example of or include the components of device1105, device 1205, or a base station 105 as described herein. The device1405 may include components for bi-directional voice and datacommunications including components for transmitting and receivingcommunications, including a communications manager 1410, a networkcommunications manager 1415, a transceiver 1420, an antenna 1425, memory1430, a processor 1440, and an inter-station communications manager1445. These components may be in electronic communication via one ormore buses (e.g., bus 1450).

The communications manager 1410 may transmit a first grant for a firstuplink transmission scheduled for transmission by a UE, identify thatthe first uplink transmission at least partially overlaps with a seconduplink transmission also scheduled for transmission by the UE, determinethe second uplink transmission will be dropped by the UE based on afirst scheduling constraint to resolve overlapping between the firstuplink transmission and the second uplink transmission, where the firstscheduling constraint is based at least in part on a first priority ofthe first uplink transmission being greater than a second priority ofthe second uplink transmission, and transmit, after the first grant, anadditional grant in accordance with a second scheduling constraint,where the second scheduling constraint relates to an additional uplinktransmission scheduled by the additional grant and scheduled to at leastpartially overlap with the first uplink transmission, and where thesecond scheduling constraint is evaluated after satisfaction of thefirst scheduling constraint to resolve overlapping between theadditional uplink transmission and the first uplink transmission afterresolving overlapping between the first uplink transmission and thesecond uplink transmission.

The communications manager 1410 may also identify that a first uplinktransmission scheduled for transmission by a UE at least partiallyoverlaps with a second uplink transmission also scheduled fortransmission by the UE, transmit an uplink cancelation indication for afrequency-time resource that at least partially overlaps with the firstuplink transmission, the second uplink transmission, or both, determinethe second uplink transmission will be dropped by the UE based on afirst scheduling constraint to resolve overlapping between the firstuplink transmission and the second uplink transmission, where the firstscheduling constraint is based at least in part on a first priority ofthe first uplink transmission being greater than a second priority ofthe second uplink transmission, and receive the first uplinktransmission in accordance with a second scheduling constraint, wherethe second scheduling constraint is evaluated after satisfaction of thefirst scheduling constraint, and where the second scheduling constraintrelates to the frequency-time resource at least partially overlappingwith the first uplink transmission, the second uplink transmission, orboth.

The communications manager 1410 may also transmit a first grant for afirst uplink transmission scheduled for transmission by a UE, transmit,after the first grant, the second grant in accordance with thescheduling constraint, and identify a scheduling constraint based on afirst priority of the first uplink transmission being greater than asecond priority of a second uplink transmission to be scheduled by asecond grant transmitted after the first grant.

The communications manager 1410 may also transmit, to a UE, an uplinkcancelation indication for a first frequency-time resource, identify ascheduling constraint that is based on whether the first frequency-timeresource overlaps with a second frequency-time resource of an uplinktransmission to be scheduled by a grant, and transmit, aftertransmission of the uplink cancelation indication, the grant for theuplink transmission in accordance with the scheduling constraint.

The network communications manager 1415 may manage communications withthe core network (e.g., via one or more wired backhaul links). Forexample, the network communications manager 1415 may manage the transferof data communications for client devices, such as one or more UEs 115.

The transceiver 1420 may communicate bi-directionally, via one or moreantennas, wired, or wireless links as described above. For example, thetransceiver 1420 may represent a wireless transceiver and maycommunicate bi-directionally with another wireless transceiver. Thetransceiver 1420 may also include a modem to modulate the packets andprovide the modulated packets to the antennas for transmission, and todemodulate packets received from the antennas.

In some cases, the wireless device may include a single antenna 1425.However, in some cases the device may have more than one antenna 1425,which may be capable of concurrently transmitting or receiving multiplewireless transmissions.

The memory 1430 may include RAM, ROM, or a combination thereof. Thememory 1430 may store computer-readable code or software 1435 includinginstructions that, when executed by a processor (e.g., the processor1440) cause the device to perform various functions described herein. Insome cases, the memory 1430 may contain, among other things, a BIOSwhich may control basic hardware or software operation such as theinteraction with peripheral components or devices.

The processor 1440 may include an intelligent hardware device, (e.g., ageneral-purpose processor, a DSP, a CPU, a microcontroller, an ASIC, anFPGA, a programmable logic device, a discrete gate or transistor logiccomponent, a discrete hardware component, or any combination thereof).In some cases, the processor 1440 may be configured to operate a memoryarray using a memory controller. In some cases, a memory controller maybe integrated into processor 1440. The processor 1440 may be configuredto execute computer-readable instructions stored in a memory (e.g., thememory 1430) to cause the device 1405 to perform various functions(e.g., functions or tasks supporting techniques for intra-UE andinter-UE cancelation of overlapping communications).

The inter-station communications manager 1445 may manage communicationswith other base station 105, and may include a controller or schedulerfor controlling communications with UEs 115 in cooperation with otherbase stations 105. For example, the inter-station communications manager1445 may coordinate scheduling for transmissions to UEs 115 for variousinterference mitigation techniques such as beamforming or jointtransmission. In some examples, the inter-station communications manager1445 may provide an X2 interface within an LTE/LTE-A wirelesscommunication network technology to provide communication between basestations 105.

The software 1435 may include instructions to implement aspects of thepresent disclosure, including instructions to support wirelesscommunications. The software 1435 may be stored in a non-transitorycomputer-readable medium such as system memory or other type of memory.In some cases, the software 1435 may not be directly executable by theprocessor 1440 but may cause a computer (e.g., when compiled andexecuted) to perform functions described herein.

FIG. 15 shows a flowchart illustrating a method 1500 that supportstechniques for intra-UE and inter-UE cancelation of overlappingcommunications in accordance with aspects of the present disclosure. Theoperations of method 1500 may be implemented by a UE 115 or itscomponents as described herein. For example, the operations of method1500 may be performed by a communications manager as described withreference to FIGS. 7 through 10 . In some examples, a UE may execute aset of instructions to control the functional elements of the UE toperform the functions described below. Additionally, or alternatively, aUE may perform aspects of the functions described below usingspecial-purpose hardware.

At 1505, the UE may receive a first grant for a first uplinktransmission scheduled for transmission by the UE. The operations of1505 may be performed according to the methods described herein. In someexamples, aspects of the operations of 1505 may be performed by a grantmanager as described with reference to FIGS. 7 through 10 .

At 1510, the UE may identify that the first uplink transmission at leastpartially overlaps with a second uplink transmission also scheduled fortransmission by the UE. The operations of 1510 may be performedaccording to the methods described herein. In some examples, aspects ofthe operations of 1510 may be performed by a scheduling manager asdescribed with reference to FIGS. 7 through 10 .

At 1515, the UE may determine to drop the second uplink transmissionbased on a first scheduling constraint to resolve overlapping betweenthe first uplink transmission and the second uplink transmission, wherethe first scheduling constraint is based at least in part on a firstpriority of the first uplink transmission being greater than a secondpriority of the second uplink transmission. The operations of 1515 maybe performed according to the methods described herein. In someexamples, aspects of the operations of 1515 may be performed by ascheduling constraint manager as described with reference to FIGS. 7through 10 .

At 1520, the UE may transmit uplink data transmissions in accordancewith a second scheduling constraint, where the second schedulingconstraint relates to an additional uplink transmission scheduled by anadditional grant received after the first grant and scheduled to atleast partially overlap with the first uplink transmission, and wherethe second scheduling constraint is evaluated after satisfaction of thefirst scheduling constraint to resolve overlapping between theadditional uplink transmission and the first uplink transmission afterresolving overlapping between the first uplink transmission and thesecond uplink transmission. The operations of 1520 may be performedaccording to the methods described herein. In some examples, aspects ofthe operations of 1520 may be performed by a transmission manager asdescribed with reference to FIGS. 7 through 10 .

FIG. 16 shows a flowchart illustrating a method 1600 that supportstechniques for intra-UE and inter-UE cancelation of overlappingcommunications in accordance with aspects of the present disclosure. Theoperations of method 1600 may be implemented by a UE 115 or itscomponents as described herein. For example, the operations of method1600 may be performed by a communications manager as described withreference to FIGS. 7 through 10 . In some examples, a UE may execute aset of instructions to control the functional elements of the UE toperform the functions described below. Additionally, or alternatively, aUE may perform aspects of the functions described below usingspecial-purpose hardware.

At 1605, the UE may identify that a first uplink transmission scheduledfor transmission by the UE at least partially overlaps with a seconduplink transmission also scheduled for transmission by the UE. Theoperations of 1605 may be performed according to the methods describedherein. In some examples, aspects of the operations of 1605 may beperformed by a scheduling manager as described with reference to FIGS. 7through 10 .

At 1610, the UE may receive an uplink cancelation indication for afrequency-time resource that at least partially overlaps with the firstuplink transmission. The operations of 1610 may be performed accordingto the methods described herein. In some examples, aspects of theoperations of 1610 may be performed by a scheduling manager as describedwith reference to FIGS. 7 through 10 .

At 1615, the UE may determine to drop the second uplink transmissionbased on a scheduling constraint to resolve overlapping between thefirst uplink transmission and the second uplink transmission, where thescheduling constraint is based at least in part on a first priority ofthe first uplink transmission being greater than a second priority ofthe second uplink transmission. The operations of 1615 may be performedaccording to the methods described herein. In some examples, aspects ofthe operations of 1615 may be performed by a scheduling constraintmanager as described with reference to FIGS. 7 through 10 .

At 1620, the UE may apply the uplink cancelation indication to the firstuplink transmission after determining that the scheduling constraint issatisfied. The operations of 1620 may be performed according to themethods described herein. In some examples, aspects of the operations of1620 may be performed by a scheduling constraint manager as describedwith reference to FIGS. 7 through 10 .

FIG. 17 shows a flowchart illustrating a method 1700 that supportstechniques for intra-UE and inter-UE cancelation of overlappingcommunications in accordance with aspects of the present disclosure. Theoperations of method 1700 may be implemented by a UE 115 or itscomponents as described herein. For example, the operations of method1700 may be performed by a communications manager as described withreference to FIGS. 7 through 10 . In some examples, a UE may execute aset of instructions to control the functional elements of the UE toperform the functions described below. Additionally, or alternatively, aUE may perform aspects of the functions described below usingspecial-purpose hardware.

At 1705, the UE may receive a first grant for a first uplinktransmission scheduled for transmission by the UE. The operations of1705 may be performed according to the methods described herein. In someexamples, aspects of the operations of 1705 may be performed by a grantmanager as described with reference to FIGS. 7 through 10 .

At 1710, the UE may receive, after receipt of the first grant, a secondgrant for a second uplink transmission scheduled for transmission by theUE. The operations of 1710 may be performed according to the methodsdescribed herein. In some examples, aspects of the operations of 1710may be performed by a grant manager as described with reference to FIGS.7 through 10 .

At 1715, the UE may determine that the first uplink transmission and thesecond uplink transmission are scheduled so as to satisfy a schedulingconstraint that is based on a first priority of the first uplinktransmission being greater than a second priority of the second uplinktransmission, the scheduling constraint further based on whether thefirst uplink transmission overlaps with the second uplink transmission.The operations of 1715 may be performed according to the methodsdescribed herein. In some examples, aspects of the operations of 1715may be performed by a scheduling constraint manager as described withreference to FIGS. 7 through 10 .

At 1720, the UE may transmit the first uplink transmission or the seconduplink transmission based on satisfaction of the scheduling constraint.The operations of 1720 may be performed according to the methodsdescribed herein. In some examples, aspects of the operations of 1720may be performed by a transmission manager as described with referenceto FIGS. 7 through 10 .

FIG. 18 shows a flowchart illustrating a method 1800 that supportstechniques for intra-UE and inter-UE cancelation of overlappingcommunications in accordance with aspects of the present disclosure. Theoperations of method 1800 may be implemented by a UE 115 or itscomponents as described herein. For example, the operations of method1800 may be performed by a communications manager as described withreference to FIGS. 7 through 10 . In some examples, a UE may execute aset of instructions to control the functional elements of the UE toperform the functions described below. Additionally, or alternatively, aUE may perform aspects of the functions described below usingspecial-purpose hardware.

At 1805, the UE may receive an uplink cancelation indication for a firstfrequency-time resource. The operations of 1805 may be performedaccording to the methods described herein. In some examples, aspects ofthe operations of 1805 may be performed by a scheduling manager asdescribed with reference to FIGS. 7 through 10 .

At 1810, the UE may receive, after receipt of the uplink cancelationindication, a grant for an uplink transmission scheduled fortransmission by the UE in a second frequency-time resource. Theoperations of 1810 may be performed according to the methods describedherein. In some examples, aspects of the operations of 1810 may beperformed by a grant manager as described with reference to FIGS. 7through 10 .

At 1815, the UE may determine that the uplink transmission is scheduledso as to satisfy a scheduling constraint that is based on whether thefirst frequency-time resource overlaps with the second frequency-timeresource. The operations of 1815 may be performed according to themethods described herein. In some examples, aspects of the operations of1815 may be performed by a scheduling constraint manager as describedwith reference to FIGS. 7 through 10 .

At 1820, the UE may determine to preempt the first frequency-timeresource and transmit the uplink transmission based on satisfaction ofthe scheduling constraint. The operations of 1820 may be performedaccording to the methods described herein. In some examples, aspects ofthe operations of 1820 may be performed by a scheduling constraintmanager as described with reference to FIGS. 7 through 10 .

FIG. 19 shows a flowchart illustrating a method 1900 that supportstechniques for intra-UE and inter-UE cancelation of overlappingcommunications in accordance with aspects of the present disclosure. Theoperations of method 1900 may be implemented by a base station 105 orits components as described herein. For example, the operations ofmethod 1900 may be performed by a communications manager as describedwith reference to FIGS. 11 through 14 . In some examples, a base stationmay execute a set of instructions to control the functional elements ofthe base station to perform the functions described below. Additionally,or alternatively, a base station may perform aspects of the functionsdescribed below using special-purpose hardware.

At 1905, the base station may transmit a first grant for a first uplinktransmission scheduled for transmission by a UE. The operations of 1905may be performed according to the methods described herein. In someexamples, aspects of the operations of 1905 may be performed by a grantmanager as described with reference to FIGS. 11 through 14 .

At 1910, the base station may identify that the first uplinktransmission at least partially overlaps with a second uplinktransmission also scheduled for transmission by the UE. The operationsof 1910 may be performed according to the methods described herein. Insome examples, aspects of the operations of 1910 may be performed by ascheduling manager as described with reference to FIGS. 11 through 14 .

At 1915, the base station may determine the second uplink transmissionwill be dropped by the UE based on a first scheduling constraint toresolve overlapping between the first uplink transmission and the seconduplink transmission, where the first scheduling constraint is based atleast in part on a first priority of the first uplink transmission beinggreater than a second priority of the second uplink transmission. Theoperations of 1915 may be performed according to the methods describedherein. In some examples, aspects of the operations of 1915 may beperformed by a scheduling constraint manager as described with referenceto FIGS. 11 through 14 .

At 1920, the base station may transmit, after the first grant, anadditional grant in accordance with a second scheduling constraint,where the second scheduling constraint relates to an additional uplinktransmission scheduled by the additional grant and scheduled to at leastpartially overlap with the first uplink transmission, and where thesecond scheduling constraint is evaluated after satisfaction of thefirst scheduling constraint to resolve overlapping between theadditional uplink transmission and the first uplink transmission afterresolving overlapping between the first uplink transmission and thesecond uplink transmission. The operations of 1920 may be performedaccording to the methods described herein. In some examples, aspects ofthe operations of 1920 may be performed by a grant manager as describedwith reference to FIGS. 11 through 14 .

FIG. 20 shows a flowchart illustrating a method 2000 that supportstechniques for intra-UE and inter-UE cancelation of overlappingcommunications in accordance with aspects of the present disclosure. Theoperations of method 2000 may be implemented by a base station 105 orits components as described herein. For example, the operations ofmethod 2000 may be performed by a communications manager as describedwith reference to FIGS. 11 through 14 . In some examples, a base stationmay execute a set of instructions to control the functional elements ofthe base station to perform the functions described below. Additionally,or alternatively, a base station may perform aspects of the functionsdescribed below using special-purpose hardware.

At 2005, the base station may identify that a first uplink transmissionscheduled for transmission by a UE at least partially overlaps with asecond uplink transmission also scheduled for transmission by the UE.The operations of 2005 may be performed according to the methodsdescribed herein. In some examples, aspects of the operations of 2005may be performed by a scheduling manager as described with reference toFIGS. 11 through 14 .

At 2010, the base station may transmit an uplink cancelation indicationfor a frequency-time resource that at least partially overlaps with thefirst uplink transmission, the second uplink transmission, or both. Theoperations of 2010 may be performed according to the methods describedherein. In some examples, aspects of the operations of 2010 may beperformed by a scheduling manager as described with reference to FIGS.11 through 14 .

At 2015, the base station may determine the second uplink transmissionwill be dropped by the UE based on a first scheduling constraint toresolve overlapping between the first uplink transmission and the seconduplink transmission, where the first scheduling constraint is based atleast in part on a first priority of the first uplink transmission beinggreater than a second priority of the second uplink transmission. Theoperations of 2015 may be performed according to the methods describedherein. In some examples, aspects of the operations of 2015 may beperformed by a scheduling constraint manager as described with referenceto FIGS. 11 through 14 .

At 2020, the base station may receive the first uplink transmission inaccordance with a second scheduling constraint, where the secondscheduling constraint is evaluated after satisfaction of the firstscheduling constraint, and where the second scheduling constraintrelates to the frequency-time resource at least partially overlappingwith the first uplink transmission, the second uplink transmission, orboth. The operations of 2020 may be performed according to the methodsdescribed herein. In some examples, aspects of the operations of 2020may be performed by an UE transmission manager as described withreference to FIGS. 11 through 14 .

FIG. 21 shows a flowchart illustrating a method 2100 that supportstechniques for intra-UE and inter-UE cancelation of overlappingcommunications in accordance with aspects of the present disclosure. Theoperations of method 2100 may be implemented by a base station 105 orits components as described herein. For example, the operations ofmethod 2100 may be performed by a communications manager as describedwith reference to FIGS. 11 through 14 . In some examples, a base stationmay execute a set of instructions to control the functional elements ofthe base station to perform the functions described below. Additionally,or alternatively, a base station may perform aspects of the functionsdescribed below using special-purpose hardware.

At 2105, the base station may transmit a first grant for a first uplinktransmission scheduled for transmission by a UE. The operations of 2105may be performed according to the methods described herein. In someexamples, aspects of the operations of 2105 may be performed by a grantmanager as described with reference to FIGS. 11 through 14 .

At 2110, the base station may identify a scheduling constraint based ona first priority of the first uplink transmission being greater than asecond priority of a second uplink transmission to be scheduled by asecond grant transmitted after the first grant. The operations of 2110may be performed according to the methods described herein. In someexamples, aspects of the operations of 2110 may be performed by ascheduling constraint manager as described with reference to FIGS. 11through 14 .

At 2115, the base station may transmit, after the first grant, thesecond grant in accordance with the scheduling constraint. Theoperations of 2115 may be performed according to the methods describedherein. In some examples, aspects of the operations of 2115 may beperformed by a grant manager as described with reference to FIGS. 11through 14 .

FIG. 22 shows a flowchart illustrating a method 2200 that supportstechniques for intra-UE and inter-UE cancelation of overlappingcommunications in accordance with aspects of the present disclosure. Theoperations of method 2200 may be implemented by a base station 105 orits components as described herein. For example, the operations ofmethod 2200 may be performed by a communications manager as describedwith reference to FIGS. 11 through 14 . In some examples, a base stationmay execute a set of instructions to control the functional elements ofthe base station to perform the functions described below. Additionally,or alternatively, a base station may perform aspects of the functionsdescribed below using special-purpose hardware.

At 2205, the base station may transmit, to a UE, an uplink cancelationindication for a first frequency-time resource. The operations of 2205may be performed according to the methods described herein. In someexamples, aspects of the operations of 2205 may be performed by ascheduling manager as described with reference to FIGS. 11 through 14 .

At 2210, the base station may identify a scheduling constraint that isbased on whether the first frequency-time resource overlaps with asecond frequency-time resource of an uplink transmission to be scheduledby a grant. The operations of 2210 may be performed according to themethods described herein. In some examples, aspects of the operations of2210 may be performed by a scheduling constraint manager as describedwith reference to FIGS. 11 through 14 .

At 2215, the base station may transmit, after transmission of the uplinkcancelation indication, the grant for the uplink transmission inaccordance with the scheduling constraint. The operations of 2215 may beperformed according to the methods described herein. In some examples,aspects of the operations of 2215 may be performed by a grant manager asdescribed with reference to FIGS. 11 through 14 .

The following provides an overview of aspects of the present disclosure:

Aspect 1: A method for wireless communication at a UE, comprising:receiving a first grant for a first uplink transmission scheduled fortransmission by the UE; identifying that the first uplink transmissionat least partially overlaps with a second uplink transmission alsoscheduled for transmission by the UE; determining to drop the seconduplink transmission based at least in part on a first schedulingconstraint to resolve overlapping between the first uplink transmissionand the second uplink transmission, wherein the first schedulingconstraint is based at least in part on a first priority of the firstuplink transmission being greater than a second priority of the seconduplink transmission; and transmitting uplink data transmissions inaccordance with a second scheduling constraint, wherein the secondscheduling constraint relates to an additional uplink transmissionscheduled by an additional grant received after the first grant andscheduled to at least partially overlap with the first uplinktransmission, and wherein the second scheduling constraint is evaluatedafter satisfaction of the first scheduling constraint to resolveoverlapping between the additional uplink transmission and the firstuplink transmission after resolving overlapping between the first uplinktransmission and the second uplink transmission.

Aspect 2: The method of aspect 1, further comprising: receiving theadditional grant; and ignoring the received additional grant based atleast in part on the second scheduling constraint until overlappingbetween the first uplink transmission and the second uplink transmissionis resolved, wherein the second uplink transmission is dropped based atleast in part on the ignoring.

Aspect 3: The method of any of aspects 1 through 2, further comprising:receiving the additional grant for the additional uplink transmissionscheduled for transmission by the UE; and determining to drop the firstuplink transmission based at least in part on the additional uplinktransmission at least partially overlapping with the first uplinktransmission, wherein the second uplink transmission and the additionaluplink transmission are non-overlapping.

Aspect 4: The method of aspect 3, wherein transmitting the uplink datatransmissions in accordance with the second scheduling constraintcomprises: piggybacking at least a portion of the first uplinktransmission on to the additional uplink transmission based at least inpart on the determination to drop the first uplink transmission; andtransmitting the additional uplink transmission and the piggybackedportion of the first uplink transmission, wherein the determination todrop the second uplink transmission is maintained based at least in parton the second scheduling constraint.

Aspect 5: The method of any of aspects 1 through 4, wherein the firstuplink transmission comprises a high priority uplink control channeltransmission or a high priority uplink shared channel transmission.

Aspect 6: The method of any of aspects 1 through 5, wherein the seconduplink transmission comprises a low priority uplink control channeltransmission, a low priority uplink shared channel transmission, or asounding reference signal transmission.

Aspect 7: The method of any of aspects 1 through 6, wherein theadditional uplink transmission comprises an additional high priorityuplink transmission.

Aspect 8: The method of any of aspects 1 through 7, wherein theadditional grant comprises a group-common grant, an uplink cancelationindication, or a slot format indicator.

Aspect 9: A method for wireless communication at a UE, comprising:identifying that a first uplink transmission scheduled for transmissionby the UE at least partially overlaps with a second uplink transmissionalso scheduled for transmission by the UE; receiving an uplinkcancelation indication for a frequency-time resource that at leastpartially overlaps with the first uplink transmission; determining todrop the second uplink transmission based at least in part on ascheduling constraint to resolve overlapping between the first uplinktransmission and the second uplink transmission, wherein the schedulingconstraint is based at least in part on a first priority of the firstuplink transmission being greater than a second priority of the seconduplink transmission; and applying the uplink cancelation indication tothe first uplink transmission after determining that the schedulingconstraint is satisfied.

Aspect 10: The method of aspect 9, wherein applying the uplinkcancelation indication to the first uplink transmission comprises:determining to drop the first uplink transmission based at least in parton the frequency-time resource at least partially overlapping with thefirst uplink transmission.

Aspect 11: The method of any of aspects 9 through 10, wherein applyingthe uplink cancelation indication to the first uplink transmissioncomprises: determining to transmit the first uplink transmission eventhough the frequency-time resource at least partially overlaps with thefirst uplink transmission.

Aspect 12: The method of any of aspects 9 through 11, wherein the firstuplink transmission comprises a high priority uplink control channeltransmission or a high priority uplink shared channel transmission.

Aspect 13: The method of any of aspects 9 through 12, wherein the seconduplink transmission comprises a low priority uplink control channeltransmission, a low priority uplink shared channel transmission, or asounding reference signal transmission.

Aspect 14: A method for wireless communication at a UE, comprising:receiving a first grant for a first uplink transmission scheduled fortransmission by the UE; receiving, after receipt of the first grant, asecond grant for a second uplink transmission scheduled for transmissionby the UE; determining that the first uplink transmission and the seconduplink transmission are scheduled so as to satisfy a schedulingconstraint that is based at least in part on a first priority of thefirst uplink transmission being greater than a second priority of thesecond uplink transmission, the scheduling constraint further based onwhether the first uplink transmission overlaps with the second uplinktransmission; and transmitting the first uplink transmission or thesecond uplink transmission based at least in part on satisfaction of thescheduling constraint.

Aspect 15: The method of aspect 14, wherein transmitting the firstuplink transmission or the second uplink transmission based at least inpart on satisfaction of the scheduling constraint comprises:transmitting the first uplink transmission.

Aspect 16: The method of aspect 15, further comprising: identifying thatthe UE has data to be included in the first uplink transmission, whereinthe first uplink transmission is transmitted based at least in part onthe UE having data to be included in the first uplink transmission.

Aspect 17: The method of any of aspects 15 through 16, furthercomprising: discarding the received second grant based at least in parton the scheduling constraint, wherein the first uplink transmission istransmitted based at least in part on the discarding.

Aspect 18: The method of any of aspects 15 through 17, wherein the firstgrant comprises a dynamic high priority grant.

Aspect 19: The method of any of aspects 14 through 18, whereintransmitting the first uplink transmission or the second uplinktransmission based at least in part on satisfaction of the schedulingconstraint comprises: transmitting the second uplink transmission.

Aspect 20: The method of aspect 19, further comprising: determining toskip the first uplink transmission based at least in part on a bufferstatus of the UE being below a threshold, wherein the second uplinktransmission is transmitted based at least in part on the determinationto skip the first uplink transmission.

Aspect 21: The method of aspect 20, wherein the first uplinktransmission comprises a high priority scheduling request or a highpriority uplink configured grant transmission.

Aspect 22: The method of any of aspects 14 through 21, wherein thescheduling constraint is satisfied based at least in part on the firstuplink transmission and the second uplink transmission beingnon-overlapping.

Aspect 23: The method of any of aspects 14 through 22, wherein the firstuplink transmission comprises a hybrid automatic repeat requestacknowledgment transmission or a channel state information transmission.

Aspect 24: The method of any of aspects 14 through 23, wherein thescheduling constraint provides that the UE does not expect to receive agrant scheduling a low priority uplink transmission that overlaps with apreviously scheduled high priority uplink transmission.

Aspect 25: A method for wireless communication at a UE, comprising:receiving an uplink cancelation indication for a first frequency-timeresource; receiving, after receipt of the uplink cancelation indication,a grant for an uplink transmission scheduled for transmission by the UEin a second frequency-time resource; determining that the uplinktransmission is scheduled so as to satisfy a scheduling constraint thatis based at least in part on whether the first frequency-time resourceoverlaps with the second frequency-time resource; and determining topreempt the first frequency-time resource and transmit the uplinktransmission based at least in part on satisfaction of the schedulingconstraint.

Aspect 26: The method of aspect 25, wherein the scheduling constraint issatisfied based at least in part on the first frequency-time resourcebeing entirely separate in time and frequency than the secondfrequency-time resource.

Aspect 27: A method for wireless communication at a base station,comprising: transmitting a first grant for a first uplink transmissionscheduled for transmission by a UE; identifying that the first uplinktransmission at least partially overlaps with a second uplinktransmission also scheduled for transmission by the UE; determining thesecond uplink transmission will be dropped by the UE based at least inpart on a first scheduling constraint to resolve overlapping between thefirst uplink transmission and the second uplink transmission, whereinthe first scheduling constraint is based at least in part on a firstpriority of the first uplink transmission being greater than a secondpriority of the second uplink transmission; and transmitting, after thefirst grant, an additional grant in accordance with a second schedulingconstraint, wherein the second scheduling constraint relates to anadditional uplink transmission scheduled by the additional grant andscheduled to at least partially overlap with the first uplinktransmission, and wherein the second scheduling constraint is evaluatedafter satisfaction of the first scheduling constraint to resolveoverlapping between the additional uplink transmission and the firstuplink transmission after resolving overlapping between the first uplinktransmission and the second uplink transmission.

Aspect 28: The method of aspect 27, further comprising: determining thetransmitted additional grant will be ignored by the UE based at least inpart on the second scheduling constraint until overlapping between thefirst uplink transmission and the second uplink transmission isresolved, wherein the second uplink transmission is dropped based atleast in part on the ignoring.

Aspect 29: The method of any of aspects 27 through 28, furthercomprising: determining the first uplink transmission will be dropped bythe UE based at least in part on transmitting the additional grant.

Aspect 30: The method of aspect 29, further comprising: receiving theadditional uplink transmission and a piggybacked portion of the firstuplink transmission.

Aspect 31: The method of any of aspects 27 through 30, wherein the firstuplink transmission comprises a high priority uplink control channeltransmission or a high priority uplink shared channel transmission.

Aspect 32: The method of any of aspects 27 through 31, wherein thesecond uplink transmission comprises a low priority uplink controlchannel transmission, a low priority uplink shared channel transmission,or a sounding reference signal transmission.

Aspect 33: The method of any of aspects 27 through 32, wherein theadditional uplink transmission comprises an additional high priorityuplink transmission.

Aspect 34: The method of any of aspects 27 through 33, wherein theadditional grant comprises a group-common grant, an uplink cancelationindication, or a slot format indicator.

Aspect 35: A method for wireless communication at a base station,comprising: identifying that a first uplink transmission scheduled fortransmission by a UE at least partially overlaps with a second uplinktransmission also scheduled for transmission by the UE; transmitting anuplink cancelation indication for a frequency-time resource that atleast partially overlaps with the first uplink transmission, the seconduplink transmission, or both; determining the second uplink transmissionwill be dropped by the UE based at least in part on a first schedulingconstraint to resolve overlapping between the first uplink transmissionand the second uplink transmission, wherein the first schedulingconstraint is based at least in part on a first priority of the firstuplink transmission being greater than a second priority of the seconduplink transmission; and receiving the first uplink transmission inaccordance with a second scheduling constraint, wherein the secondscheduling constraint is evaluated after satisfaction of the firstscheduling constraint, and wherein the second scheduling constraintrelates to the frequency-time resource at least partially overlappingwith the first uplink transmission, the second uplink transmission, orboth.

Aspect 36: The method of aspect 35, wherein receiving the first uplinktransmission in accordance with the second scheduling constraintcomprises: determining the first uplink transmission will be dropped bythe UE based at least in part on the frequency-time resource at leastpartially overlapping with the first uplink transmission.

Aspect 37: The method of any of aspects 35 through 36, wherein receivingthe first uplink transmission in accordance with the second schedulingconstraint comprises: receiving the first uplink transmission based atleast in part on the frequency-time resource at least partiallyoverlapping with the second uplink transmission.

Aspect 38: The method of any of aspects 35 through 37, wherein the firstuplink transmission comprises a high priority uplink control channeltransmission or a high priority uplink shared channel transmission.

Aspect 39: The method of any of aspects 35 through 38, wherein thesecond uplink transmission comprises a low priority uplink controlchannel transmission, a low priority uplink shared channel transmission,or a sounding reference signal transmission.

Aspect 40: A method for wireless communication at a base station,comprising: transmitting a first grant for a first uplink transmissionscheduled for transmission by a UE; identifying a scheduling constraintbased at least in part on a first priority of the first uplinktransmission being greater than a second priority of a second uplinktransmission to be scheduled by a second grant transmitted after thefirst grant; and transmitting, after the first grant, the second grantin accordance with the scheduling constraint.

Aspect 41: The method of aspect 40, further comprising: receiving thefirst uplink transmission based at least in part on the transmittedfirst grant.

Aspect 42: The method of aspect 41, wherein the first grant comprises adynamic high priority grant.

Aspect 43: The method of any of aspects 40 through 42, furthercomprising: receiving the second uplink transmission based at least inpart on the transmitted additional grant.

Aspect 44: The method of aspect 43, wherein the first uplinktransmission comprises a high priority scheduling request or a highpriority uplink configured grant transmission.

Aspect 45: The method of any of aspects 43 through 44, furthercomprising: determining the UE skipped the first uplink transmissionbased at least in part on receiving the second uplink transmission,wherein the determination that the UE skipped the first uplinktransmission is based at least in part on a buffer status of the UEbeing below a threshold.

Aspect 46: The method of any of aspects 40 through 45, wherein thescheduling constraint further relates to the second uplink transmissionscheduled to overlap with the first uplink transmission.

Aspect 47: The method of any of aspects 40 through 46, wherein the firstuplink transmission comprises a hybrid automatic repeat requestacknowledgment transmission or a channel state information transmission.

Aspect 48: The method of any of aspects 40 through 47, wherein thescheduling constraint provides that the UE does not expect to receive agrant scheduling a low priority uplink transmission that overlaps with apreviously scheduled high priority uplink transmission.

Aspect 49: A method for wireless communication at a base station,comprising: transmitting, to a UE, an uplink cancelation indication fora first frequency-time resource; identifying a scheduling constraintthat is based at least in part on whether the first frequency-timeresource overlaps with a second frequency-time resource of an uplinktransmission to be scheduled by a grant; and transmitting, aftertransmission of the uplink cancelation indication, the grant for theuplink transmission in accordance with the scheduling constraint.

Aspect 50: The method of aspect 49, wherein the scheduling constraint issatisfied based at least in part on the first frequency-time resourcebeing entirely separate in time and frequency than the secondfrequency-time resource.

Aspect 51: An apparatus for wireless communication at a UE, comprising aprocessor; memory coupled with the processor; and instructions stored inthe memory and executable by the processor to cause the apparatus toperform a method of any of aspects 1 through 8.

Aspect 52: An apparatus for wireless communication at a UE, comprisingat least one means for performing a method of any of aspects 1 through8.

Aspect 53: A non-transitory computer-readable medium storing code forwireless communication at a UE, the code comprising instructionsexecutable by a processor to perform a method of any of aspects 1through 8.

Aspect 54: An apparatus for wireless communication at a UE, comprising aprocessor; memory coupled with the processor; and instructions stored inthe memory and executable by the processor to cause the apparatus toperform a method of any of aspects 9 through 13.

Aspect 55: An apparatus for wireless communication at a UE, comprisingat least one means for performing a method of any of aspects 9 through13.

Aspect 56: A non-transitory computer-readable medium storing code forwireless communication at a UE, the code comprising instructionsexecutable by a processor to perform a method of any of aspects 9through 13.

Aspect 57: An apparatus for wireless communication at a UE, comprising aprocessor; memory coupled with the processor; and instructions stored inthe memory and executable by the processor to cause the apparatus toperform a method of any of aspects 14 through 24.

Aspect 58: An apparatus for wireless communication at a UE, comprisingat least one means for performing a method of any of aspects 14 through24.

Aspect 59: A non-transitory computer-readable medium storing code forwireless communication at a UE, the code comprising instructionsexecutable by a processor to perform a method of any of aspects 14through 24.

Aspect 60: An apparatus for wireless communication at a UE, comprising aprocessor; memory coupled with the processor; and instructions stored inthe memory and executable by the processor to cause the apparatus toperform a method of any of aspects 25 through 26.

Aspect 61: An apparatus for wireless communication at a UE, comprisingat least one means for performing a method of any of aspects 25 through26.

Aspect 62: A non-transitory computer-readable medium storing code forwireless communication at a UE, the code comprising instructionsexecutable by a processor to perform a method of any of aspects 25through 26.

Aspect 63: An apparatus for wireless communication at a base station,comprising a processor; memory coupled with the processor; andinstructions stored in the memory and executable by the processor tocause the apparatus to perform a method of any of aspects 27 through 34.

Aspect 64: An apparatus for wireless communication at a base station,comprising at least one means for performing a method of any of aspects27 through 34.

Aspect 65: A non-transitory computer-readable medium storing code forwireless communication at a base station, the code comprisinginstructions executable by a processor to perform a method of any ofaspects 27 through 34.

Aspect 66: An apparatus for wireless communication at a base station,comprising a processor; memory coupled with the processor; andinstructions stored in the memory and executable by the processor tocause the apparatus to perform a method of any of aspects 35 through 39.

Aspect 67: An apparatus for wireless communication at a base station,comprising at least one means for performing a method of any of aspects35 through 39.

Aspect 68: A non-transitory computer-readable medium storing code forwireless communication at a base station, the code comprisinginstructions executable by a processor to perform a method of any ofaspects 35 through 39.

Aspect 69: An apparatus for wireless communication at a base station,comprising a processor; memory coupled with the processor; andinstructions stored in the memory and executable by the processor tocause the apparatus to perform a method of any of aspects 40 through 48.

Aspect 70: An apparatus for wireless communication at a base station,comprising at least one means for performing a method of any of aspects40 through 48.

Aspect 71: A non-transitory computer-readable medium storing code forwireless communication at a base station, the code comprisinginstructions executable by a processor to perform a method of any ofaspects 40 through 48.

Aspect 72: An apparatus for wireless communication at a base station,comprising a processor; memory coupled with the processor; andinstructions stored in the memory and executable by the processor tocause the apparatus to perform a method of any of aspects 49 through 50.

Aspect 73: An apparatus for wireless communication at a base station,comprising at least one means for performing a method of any of aspects49 through 50.

Aspect 74: A non-transitory computer-readable medium storing code forwireless communication at a base station, the code comprisinginstructions executable by a processor to perform a method of any ofaspects 49 through 50.

It should be noted that the methods described herein describe possibleimplementations, and that the operations and the steps may be rearrangedor otherwise modified and that other implementations are possible.Further, aspects from two or more of the methods may be combined.

Although aspects of an LTE, LTE-A, LTE-A Pro, or NR system may bedescribed for purposes of example, and LTE, LTE-A, LTE-A Pro, or NRterminology may be used in much of the description, the techniquesdescribed herein are applicable beyond LTE, LTE-A, LTE-A Pro, or NRnetworks. For example, the described techniques may be applicable tovarious other wireless communications systems such as Ultra MobileBroadband (UMB), Institute of Electrical and Electronics Engineers(IEEE) 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE 802.20, Flash-OFDM, aswell as other systems and radio technologies not explicitly mentionedherein.

Information and signals described herein may be represented using any ofa variety of different technologies and techniques. For example, data,instructions, commands, information, signals, bits, symbols, and chipsthat may be referenced throughout the description may be represented byvoltages, currents, electromagnetic waves, magnetic fields or particles,optical fields or particles, or any combination thereof.

The various illustrative blocks and components described in connectionwith the disclosure herein may be implemented or performed with ageneral-purpose processor, a DSP, an ASIC, a CPU, an FPGA or otherprogrammable logic device, discrete gate or transistor logic, discretehardware components, or any combination thereof designed to perform thefunctions described herein. A general-purpose processor may be amicroprocessor, but in the alternative, the processor may be anyprocessor, controller, microcontroller, or state machine. A processormay also be implemented as a combination of computing devices (e.g., acombination of a DSP and a microprocessor, multiple microprocessors, oneor more microprocessors in conjunction with a DSP core, or any othersuch configuration).

The functions described herein may be implemented in hardware, softwareexecuted by a processor, firmware, or any combination thereof. Ifimplemented in software executed by a processor, the functions may bestored on or transmitted over as one or more instructions or code on acomputer-readable medium. Other examples and implementations are withinthe scope of the disclosure and appended claims. For example, due to thenature of software, functions described herein may be implemented usingsoftware executed by a processor, hardware, firmware, hardwiring, orcombinations of any of these. Features implementing functions may alsobe physically located at various positions, including being distributedsuch that portions of functions are implemented at different physicallocations.

Computer-readable media includes both non-transitory computer storagemedia and communication media including any medium that facilitatestransfer of a computer program from one place to another. Anon-transitory storage medium may be any available medium that may beaccessed by a general-purpose or special purpose computer. By way ofexample, and not limitation, non-transitory computer-readable media mayinclude random-access memory (RAM), read-only memory (ROM), electricallyerasable programmable ROM (EEPROM), flash memory, compact disk (CD) ROMor other optical disk storage, magnetic disk storage or other magneticstorage devices, or any other non-transitory medium that may be used tocarry or store desired program code means in the form of instructions ordata structures and that may be accessed by a general-purpose orspecial-purpose computer, or a general-purpose or special-purposeprocessor. Also, any connection is properly termed a computer-readablemedium. For example, if the software is transmitted from a website,server, or other remote source using a coaxial cable, fiber optic cable,twisted pair, digital subscriber line (DSL), or wireless technologiessuch as infrared, radio, and microwave, then the coaxial cable, fiberoptic cable, twisted pair, DSL, or wireless technologies such asinfrared, radio, and microwave are included in the definition ofcomputer-readable medium. Disk and disc, as used herein, include CD,laser disc, optical disc, digital versatile disc (DVD), floppy disk andBlu-ray disc where disks usually reproduce data magnetically, whilediscs reproduce data optically with lasers. Combinations of the aboveare also included within the scope of computer-readable media.

As used herein, including in the claims, “or” as used in a list of items(e.g., a list of items prefaced by a phrase such as “at least one of” or“one or more of”) indicates an inclusive list such that, for example, alist of at least one of A, B, or C means A or B or C or AB or AC or BCor ABC (i.e., A and B and C). Also, as used herein, the phrase “basedon” shall not be construed as a reference to a closed set of conditions.For example, an example step that is described as “based on condition A”may be based on both a condition A and a condition B without departingfrom the scope of the present disclosure. In other words, as usedherein, the phrase “based on” shall be construed in the same manner asthe phrase “based at least in part on.”

In the appended figures, similar components or features may have thesame reference label. Further, various components of the same type maybe distinguished by following the reference label by a dash and a secondlabel that distinguishes among the similar components. If just the firstreference label is used in the specification, the description isapplicable to any one of the similar components having the same firstreference label irrespective of the second reference label, or othersubsequent reference label.

The description set forth herein, in connection with the appendeddrawings, describes example configurations and does not represent allthe examples that may be implemented or that are within the scope of theclaims. The term “example” used herein means “serving as an example,instance, or illustration,” and not “preferred” or “advantageous overother examples.” The detailed description includes specific details forthe purpose of providing an understanding of the described techniques.These techniques, however, may be practiced without these specificdetails. In some instances, known structures and devices are shown inblock diagram form in order to avoid obscuring the concepts of thedescribed examples.

The description herein is provided to enable a person having ordinaryskill in the art to make or use the disclosure. Various modifications tothe disclosure will be apparent to a person having ordinary skill in theart, and the generic principles defined herein may be applied to othervariations without departing from the scope of the disclosure. Thus, thedisclosure is not limited to the examples and designs described herein,but is to be accorded the broadest scope consistent with the principlesand novel features disclosed herein.

What is claimed is:
 1. An apparatus for wireless communication at a userequipment (UE), comprising: a processor, memory coupled with theprocessor; and instructions stored in the memory and executable by theprocessor to cause the apparatus to: receive a first grant for a firstuplink transmission scheduled for transmission by the UE; receive, afterreceipt of the first grant, a second grant for a second uplinktransmission scheduled for transmission by the UE; determine that thefirst uplink transmission and the second uplink transmission arescheduled so as to satisfy a scheduling constraint that is based atleast in part on a first priority of the first uplink transmission beinggreater than a second priority of the second uplink transmission, thescheduling constraint further based on whether the first uplinktransmission overlaps with the second uplink transmission, wherein thescheduling constraint indicates a probability that the UE will receive agrant scheduling a low priority uplink transmission that overlaps with apreviously scheduled high priority uplink transmission; and transmit thefirst uplink transmission or the second uplink transmission based atleast in part on satisfaction of the scheduling constraint.
 2. Theapparatus of claim 1, wherein the instructions to transmit the firstuplink transmission or the second uplink transmission based at least inpart on satisfaction of the scheduling constraint are executable by theprocessor to cause the apparatus to: transmit the first uplinktransmission.
 3. The apparatus of claim 2, wherein the instructions arefurther executable by the processor to cause the apparatus to: identifythat the UE has data to be included in the first uplink transmission,wherein the first uplink transmission is transmitted based at least inpart on the UE having data to be included in the first uplinktransmission.
 4. The apparatus of claim 2, wherein the instructions arefurther executable by the processor to cause the apparatus to: discardthe received second grant based at least in part on the schedulingconstraint, wherein the first uplink transmission is transmitted basedat least in part on the discarding.
 5. The apparatus of claim 1, whereinthe instructions to transmit the first uplink transmission or the seconduplink transmission based at least in part on satisfaction of thescheduling constraint are executable by the processor to cause theapparatus to: transmit the second uplink transmission.
 6. The apparatusof claim 5, wherein the instructions are further executable by theprocessor to cause the apparatus to: determine to skip the first uplinktransmission based at least in part on a buffer status of the UE beingbelow a threshold, wherein the second uplink transmission is transmittedbased at least in part on the determination to skip the first uplinktransmission.
 7. The apparatus of claim 6, wherein the first uplinktransmission comprises a high priority scheduling request or a highpriority uplink configured grant transmission.
 8. The apparatus of claim1, wherein the scheduling constraint is satisfied based at least in parton the first uplink transmission and the second uplink transmissionbeing non-overlapping.
 9. The apparatus of claim 1, wherein the firstuplink transmission comprises a hybrid automatic repeat requestacknowledgment transmission that is to be transmitted in response to asemi-persistently scheduled physical downlink shared channeltransmission.
 10. The apparatus of claim 1, wherein the first uplinktransmission comprises a semi-persistent channel state informationtransmission.
 11. An apparatus for wireless communication at a userequipment (UE), comprising: a processor, memory coupled with theprocessor; and instructions stored in the memory and executable by theprocessor to cause the apparatus to: receive an uplink cancelationindication for a first frequency-time resource; receive, after receiptof the uplink cancelation indication, a grant for an uplink transmissionscheduled for transmission by the UE in a second frequency-timeresource; determine that the uplink transmission is scheduled so as tosatisfy a scheduling constraint that is based at least in part onwhether the first frequency-time resource overlaps with the secondfrequency-time resource, wherein the scheduling constraint indicates aprobability that the UE will receive a grant scheduling a high priorityuplink transmission that overlaps with a previously canceledfrequency-time resource; and determine to preempt the firstfrequency-time resource and transmit the uplink transmission based atleast in part on satisfaction of the scheduling constraint.
 12. Theapparatus of claim 11, wherein: the uplink transmission is a physicaluplink shared channel transmission or a sounding reference signal; andthe scheduling constraint is satisfied based at least in part on thefirst frequency-time resource being entirely separate in time from thesecond frequency-time resource.
 13. An apparatus for wirelesscommunication at a base station, comprising: a processor, memory coupledwith the processor; and instructions stored in the memory and executableby the processor to cause the apparatus to: transmit a first grant for afirst uplink transmission scheduled for transmission by a user equipment(UE); identify a scheduling constraint based at least in part on a firstpriority of the first uplink transmission being greater than a secondpriority of a second uplink transmission to be scheduled by a secondgrant transmitted after the first grant, wherein the schedulingconstraint indicates a probability that the UE will receive a grantscheduling a low priority uplink transmission that overlaps with apreviously scheduled high priority uplink transmission; and transmit,after the first grant, the second grant in accordance with thescheduling constraint.
 14. The apparatus of claim 13, wherein theinstructions are further executable by the processor to cause theapparatus to: receive the first uplink transmission based at least inpart on the transmitted first grant.
 15. The apparatus of claim 13,wherein the instructions are further executable by the processor tocause the apparatus to: receive the second uplink transmission based atleast in part on the transmitted second grant.
 16. The apparatus ofclaim 15, wherein the instructions are further executable by theprocessor to cause the apparatus to: determine the UE skipped the firstuplink transmission based at least in part on receiving the seconduplink transmission, wherein the determination that the UE skipped thefirst uplink transmission is based at least in part on a buffer statusof the UE being below a threshold.
 17. The apparatus of claim 13,wherein the scheduling constraint further relates to the second uplinktransmission scheduled to overlap with the first uplink transmission.18. The apparatus of claim 13, wherein the first uplink transmissioncomprises a hybrid automatic repeat request acknowledgment transmissionthat is to be transmitted in response to a semi-persistently scheduledphysical downlink shared channel transmission or a semi-persistentchannel state information transmission.
 19. The apparatus of claim 13,wherein the scheduling constraint provides that the UE does not expectto receive a grant scheduling a low priority uplink transmission thatoverlaps with a previously scheduled high priority uplink transmission.